[GitHub] spark issue #12930: [SPARK-15153] [ML] [SparkR] Fix SparkR spark.naiveBayes ...

2016-10-11 Thread yanboliang
Github user yanboliang commented on the issue: https://github.com/apache/spark/pull/12930 Move the new fix to #15431 which leverages ```RFormula forceIndexLabel```, more succinct. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] spark issue #12930: [SPARK-15153] [ML] [SparkR] Fix SparkR spark.naiveBayes ...

2016-10-07 Thread jkbradley
Github user jkbradley commented on the issue: https://github.com/apache/spark/pull/12930 Oh! Now I see the JIRA's linked JIRA. I agree that updating RFormula is a better solution and that we can close this PR. I'll check out the other PR. --- If your project is set up for it, you

[GitHub] spark issue #12930: [SPARK-15153] [ML] [SparkR] Fix SparkR spark.naiveBayes ...

2016-10-07 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/spark/pull/12930 Should/Would this be better if this is handled in the RFormula level? I could see other models could benefit from this too, in addition to just R. --- If your project is set up for it, you can

[GitHub] spark issue #12930: [SPARK-15153] [ML] [SparkR] Fix SparkR spark.naiveBayes ...

2016-10-07 Thread jkbradley
Github user jkbradley commented on the issue: https://github.com/apache/spark/pull/12930 It's still a problem. (I just tried the unit test on master.) Sorry for the delay @yanboliang ! --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] spark issue #12930: [SPARK-15153] [ML] [SparkR] Fix SparkR spark.naiveBayes ...

2016-08-11 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/spark/pull/12930 Do we still need this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and