Re: Spark Improvement Proposals

The current draft LGTM. I agree some of the various concerns may need to be addressed in the future, depending on how SPIPs progress in practice. If others agree, let's put it to a vote and revisit the proposal in a few months. Joseph On Fri, Feb 24, 2017 at 5:35 AM, Cody Koeninger

Re: Nightly builds for master branch have been failing

I spotted the problem and it appears to be a misconfiguration / missing entry in the template which generates the packaging jobs. I've corrected the problem but now the jobs appear to be hanging / flaking on the Git clone. Hopefully this is just a transient issue, so let's retry tonight and see

Re: [Spark Namespace]: Expanding Spark ML under Different Namespace?

Regarding logging, Graphframes makes a simple wrapper this way: https://github.com/graphframes/graphframes/blob/master/src/main/scala/org/ graphframes/Logging.scala Regarding the UDTs, they have been hidden to be reworked for Datasets, the reasons being detailed here [1]. Can you describe your

Re: Spark Improvement Proposals

It's been a week since any further discussion. Do PMC members think the current draft is OK to vote on? On Fri, Feb 17, 2017 at 10:41 PM, vaquar khan wrote: > I like document and happy to see SPIP draft version however i feel shepherd > role is again hurdle in process

Nightly builds for master branch have been failing

Nightly builds for master branch have been failing: https://amplab.cs.berkeley.edu/jenkins/job/spark-master-maven-snapshots/buildTimeTrend It'd be great if we can get this fixed. Thanks. Cheers, Liwei

Re: Feedback on MLlib roadmap process proposal

FYI I've started going through a few of the top Watched JIRAs and tried to identify those that are obviously stale and can probably be closed, to try to clean things up a bit. On Thu, 23 Feb 2017 at 21:38 Tim Hunter wrote: > As Sean wrote very nicely above, the changes