I would definitely be in favor of moving to Spark 2.0 as early as possible. This will allow SystemML to be current with cutting edge Spark. It would be nice to focus our efforts on the latest Spark.
Deron On Tue, Aug 2, 2016 at 12:05 PM, <dusenberr...@gmail.com> wrote: > I'm in favor of moving to Spark 2.0 now, meaning that our upcoming release > would include both new features and 2.0 support. 0.10 has plenty of > functionality for any existing 1.x users. > > -Mike > > -- > > Mike Dusenberry > GitHub: github.com/dusenberrymw > LinkedIn: linkedin.com/in/mikedusenberry > > Sent from my iPhone. > > > > On Aug 2, 2016, at 11:44 AM, Glenn Weidner <gweid...@us.ibm.com> wrote: > > > > > > > > In the "[DISCUSS] SystemML 0.11 release" thread, native frame support and > > API updates such as new MLContext were identified as main new features > for > > the release. In addition, support for Spark 2.0.0 was targeted. > > Note code changes required for Spark 2.0.0 are not backward compatible to > > earlier Spark versions (e.g., 1.6.2) so starting separate mail thread for > > anyone to raise objections/alternatives for migrating to Spark 2.0.0. > > > > One possible option is to do a release to include the new Apache SystemML > > features before migrating to Spark 2.0.0. However, it seems better to > have > > the next Apache SystemML release compatible with latest Spark version > > 2.0.0. The Apache SystemML 0.10 release from June can be used with > earlier > > versions of Spark. > > > > Regards, > > Glenn >
