I think this is a great idea so that we can simplify the official release and
reduce confusion for potential users. Certainly we can still retain the
potential to build the extra artifacts locally, just like Spark current does.
I would also like to suggest that we move away from the current
On Tue, Aug 23, 2016 at 3:51 PM, Deron Eriksson
wrote:
> To simplify release candidate validation, I would like to propose that the
> distribution profile only builds the following 7 (out of the current
> included 10) artifacts:
>
>
Center
> office: (408) 927 2208; T/L: 457 2208
> e-mail: reinw...@us.ibm.com
>
>
>
> From: dusenberr...@gmail.com
> To: dev@systemml.incubator.apache.org
> Date: 08/17/2016 04:52 PM
> Subject:Re: [DISCUSS] SystemML with Spark 2.0 support and roadmap
>
>
>
/L: 457 2208
e-mail: reinw...@us.ibm.com
From: dusenberr...@gmail.com
To: dev@systemml.incubator.apache.org
Date: 08/17/2016 04:52 PM
Subject:Re: [DISCUSS] SystemML with Spark 2.0 support and roadmap
+1
This sounds like a good plan to allow us to continue supporting the Spark
DF
> file.
> If there is any other better option please let me know.
>
>
> -Arvind
>
>
>
>
>
> - Forwarded Message -
> *From:* Acs S <ac...@yahoo.com.INVALID>
> *To:* Dev <dev@systemml.incubator.apache.org>
> *Sent:* Wednesday, August 17, 2016
Spark 2.0 has released, we need to support SystemML on Spark 2.0 to be uptodate
with latest version of Spark. This brings us a challenge to support our
consumers until they move to Spark 2.0.Based on some brainstorming, I can
propose following options to keep SystemML being supported on latest