Re: Welcoming two new committers

Thanks everyone. I look forward to continuing to work with all of you! 2014-08-08 3:23 GMT-07:00 Prashant Sharma : > Congratulations Andrew and Joey. > > Prashant Sharma > > > > > On Fri, Aug 8, 2014 at 2:10 PM, Xiangrui Meng wrote: > >> Congrats, Joey & Andrew!! >> >> -Xiangrui >> >> On Fri, A

Re: Using mllib-1.1.0-SNAPSHOT on Spark 1.0.1

Hi Xiangrui, Based on your suggestion I moved core and mllib both to 1.1.0-SNAPSHOT...I am still getting class cast exception: Exception in thread "main" org.apache.spark.SparkException: Job aborted due to stage failure: Task 249 in stage 52.0 failed 4 times, most recent failure: Lost task 249.3

RE: Welcoming two new committers

Congrats Joey and Andrew! Sent from my Windows Phone From: Andrew Or Sent: ‎8/‎9/‎2014 2:43 AM To: Prashant Sharma Cc: Xiangrui Meng; Christopher Nguyen; Jo

Re: Unit tests in < 5 minutes

Issue with supporting this imo is the fact that scala-test uses the same vm for all the tests (surefire plugin supports fork, but scala-test ignores it iirc). So different tests would initialize different spark context, and can potentially step on each others toes. Regards, Mridul On Fri, Aug 8,

Re: Using mllib-1.1.0-SNAPSHOT on Spark 1.0.1

I validated that I can reproduce this problem with master as well (without adding any of my mllib changes)... I separated mllib jar from assembly, deploy the assembly and then I supply the mllib jar as --jars option to spark-submit... I get this error: 14/08/09 12:49:32 INFO DAGScheduler: Failed

Re: Using mllib-1.1.0-SNAPSHOT on Spark 1.0.1

I was having this same problem early this week and had to include my changes in the assembly. On Sat, Aug 9, 2014 at 9:59 AM, Debasish Das wrote: > I validated that I can reproduce this problem with master as well (without > adding any of my mllib changes)... > > I separated mllib jar from asse

Re: Using mllib-1.1.0-SNAPSHOT on Spark 1.0.1

Including mllib inside assembly worked fine...If I deploy only the core and send mllib as --jars then this problem shows up... Xiangrui could you please comment if it is a bug or expected behavior ? I will create a JIRA if this needs to be tracked... On Sat, Aug 9, 2014 at 11:01 AM, Matt Forbes

Re: Using mllib-1.1.0-SNAPSHOT on Spark 1.0.1

Actually nope it did not work fine... With multiple ALS iteration, I am getting the same error (with or without my mllib changes) Exception in thread "main" org.apache.spark.SparkException: Job aborted due to stage failure: Task 206 in stage 52.0 failed 4 times, most recent failure: Lost task