I think the question for me would be does this only happen when you call partitionBy, or always? And how common do you expect calls to partitionBy to be? If we can wait for 1.0.1 then I’d wait on this one.
Matei On May 26, 2014, at 10:47 PM, Patrick Wendell <pwend...@gmail.com> wrote: > Hey Ankur, > > That does seem like a good fix, but right now we are only blocking the > release on major regressions that affect all components. So I don't > think this is sufficient to block it from going forward and cutting a > new candidate. This is because we are in the very late stage of the > release. > > We can slot that for the 1.0.1 release and merge it into the 1.0 > branch so people can get access to the fix easily. > > On Mon, May 26, 2014 at 6:50 PM, ankurdave <ankurd...@gmail.com> wrote: >> -1 >> >> I just fixed SPARK-1931 <https://issues.apache.org/jira/browse/SPARK-1931> >> , which was a critical bug in Graph#partitionBy. Since this is an important >> part of the GraphX API, I think Spark 1.0.0 should include the fix: >> https://github.com/apache/spark/pull/885. >> >> >> >> -- >> View this message in context: >> http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Apache-Spark-1-0-0-RC11-tp6797p6802.html >> Sent from the Apache Spark Developers List mailing list archive at >> Nabble.com.
