You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/09/30 11:01:20 UTC
[jira] [Commented] (SPARK-17744) Parity check between the ml and
mllib test suites for NB
[ https://issues.apache.org/jira/browse/SPARK-17744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535694#comment-15535694 ]
Sean Owen commented on SPARK-17744:
-----------------------------------
For a lot of these 'audit' or 'check' JIRAs, can I suggest it's often easier just to do the audit and if there are issues, open a JIRA? I can see some value if it must be there to block a release but not so much like this.
> Parity check between the ml and mllib test suites for NB
> --------------------------------------------------------
>
> Key: SPARK-17744
> URL: https://issues.apache.org/jira/browse/SPARK-17744
> Project: Spark
> Issue Type: Improvement
> Components: ML
> Reporter: zhengruifeng
>
> Parity check between the ml and mllib test suites, and complement missing test cases for ml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org