(I don't think 2.0.2 will be released for a while if at all but that's not what you're asking I think)
It's a fairly safe change, but also isn't exactly a fix in my opinion. Because there are some other changes to make it all work for SPARC, I think it's more realistic to look to the 2.1.0 release anyway, which is likely to come first. On Mon, Oct 17, 2016 at 4:09 PM Erik O'Shaughnessy < erik.oshaughne...@oracle.com> wrote: > I would very much like to see SPARK-16962 included in 2.0.2 as it addresses > unaligned memory access patterns that crash non-x86 platforms. I believe > this falls in the category of "correctness fix". We (Oracle SAE) have > applied the fixes for SPARK-16962 to branch-2.0 and have not encountered > any > problems on SPARC or x86 architectures attributable to unaligned accesses. > Including this fix will allow Oracle SPARC customers to run Apache Spark > without fear of crashing, expanding the reach of Apache Spark and making my > life a little easier :) > > erik.oshaughne...@oracle.com > > > > -- > View this message in context: > http://apache-spark-developers-list.1001551.n3.nabble.com/cutting-2-0-2-tp19473p19482.html > Sent from the Apache Spark Developers List mailing list archive at > Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
