systemml-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Acs S <>
Subject Re: [DISCUSS] SystemML releases 0.11 and 1.0
Date Tue, 20 Sep 2016 05:39:29 GMT
I would agree to most of the part except that there would be need to have SystemML support
on Spark 2.0 for "Spark As A Service" (or DSX). I haven't seen formal request for Spark 2.0
support from SAAS/DSX team yet, but I heard they are targeting 09/30. In such situation,
I would like to  prioritize SystemML support on Spark 2.0 around same time as 0.11 release.

      From: Glenn Weidner <>
 Sent: Monday, September 19, 2016 10:07 PM
 Subject: Re: [DISCUSS] SystemML releases 0.11 and 1.0


Berthold Reinwald---09/19/2016 09:52:26 PM---+1. I'd even consider not fixing old MLContext
releated issues.

From: Berthold Reinwald/Almaden/IBM@IBMUS
Date: 09/19/2016 09:52 PM
Subject: Re: [DISCUSS] SystemML releases 0.11 and 1.0


I'd even consider not fixing old MLContext releated issues.

Berthold Reinwald
IBM Almaden Research Center
office: (408) 927 2208; T/L: 457 2208

From:   Matthias Boehm/Almaden/IBM@IBMUS
To:     dev <>
Date:   09/19/2016 08:21 PM
Subject:        [DISCUSS] SystemML releases 0.11 and 1.0

Hi all,

we already discussed and agreed that it would be good to make our next
release relatively soon. However, there was also a discussion around 
the major 1.0 release but this would require substantially more time
because it is our opportunity to remove APIs and cleanup the language.

I'd like to propose the following: let's release a 0.11 release in the 
couple of weeks, targeting at Spark 1.x including the old and new 
APIs as well as both file-based and frame-based transform. Subsequently, 
can focus on our major 1.0 release, including the support for Spark 2.x,
the removal of the old MLContext API, and the removal of the file-based
transform functionalities. Hopefully we get compression and GPU support
into production-ready state until the 1.0 release too.

The next step would be to collect open issues for the 0.11 release. From 
perspective, this should mostly center around documentation, robustness 
performance of the new MLContext API and frame support as well as the
simplification of our build process.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message