Re: Odp.: Spark Improvement Proposals

Thanks for picking up on this. Maybe I fail at google docs, but I can't see any edits on the document you linked. Regarding lazy consensus, if the board in general has less of an issue with that, sure. As long as it is clearly announced, lasts at least 72 hours, and has a clear outcome. The

Re: Odp.: Spark Improvement Proposals

I just looked through the entire thread again tonight - there are a lot of great ideas being discussed. Thanks Cody for taking the first crack at the proposal. I want to first comment on the context. Spark is one of the most innovative and important projects in (big) data -- overall technical

Re: Odp.: Spark Improvement Proposals

Most things looked OK to me too, although I do plan to take a closer look after Nov 1st when we cut the release branch for 2.1. On Mon, Oct 31, 2016 at 3:12 PM, Marcelo Vanzin wrote: > The proposal looks OK to me. I assume, even though it's not explicitly > called, that

Re: Odp.: Spark Improvement Proposals

The proposal looks OK to me. I assume, even though it's not explicitly called, that voting would happen by e-mail? A template for the proposal document (instead of just a bullet nice) would also be nice, but that can be done at any time. BTW, shameless plug: I filed SPARK-18085 which I consider a

Re: Odp.: Spark Improvement Proposals

I agree, we should push forward on this. I think there is enough consensus to call a vote, unless someone else thinks that there is more to discuss? rb On Mon, Oct 31, 2016 at 10:34 AM, Cody Koeninger wrote: > Now that spark summit europe is over, are any committers

Re: Odp.: Spark Improvement Proposals

Now that spark summit europe is over, are any committers interested in moving forward with this? https://github.com/koeninger/spark-1/blob/SIP-0/docs/spark-improvement-proposals.md Or are we going to let this discussion die on the vine? On Mon, Oct 17, 2016 at 10:05 AM, Tomasz Gawęda

Odp.: Spark Improvement Proposals

Maybe my mail was not clear enough. I didn't want to write "lets focus on Flink" or any other framework. The idea with benchmarks was to show two things: - why some people are doing bad PR for Spark - how - in easy way - we can change it and show that Spark is still on the top No more, no