[VOTE] Release Apache Spark 2.0.2 (RC3)

Please vote on releasing the following candidate as Apache Spark version 2.0.2. The vote is open until Thu, Nov 10, 2016 at 22:00 PDT and passes if a majority of at least 3+1 PMC votes are cast. [ ] +1 Release this package as Apache Spark 2.0.2 [ ] -1 Do not release this package because ... The

[ANNOUNCE] Announcing Apache Spark 1.6.3

We are happy to announce the availability of Spark 1.6.3! This maintenance release includes fixes across several areas of Spark and encourage users on the 1.6.x line to upgrade to 1.6.3. Head to the project's download page to download the new version: http://spark.apache.org/downloads.html

Re: Handling questions in the mailing lists

To help track and get the verbiage for the Spark community page and welcome email jump started, here's a working document for us to work with: https://docs.google.com/document/d/1N0pKatcM15cqBPqFWCqIy6jdgNzIoacZlYDCjufBh2s/edit# Hope this will help us collaborate on this stuff a little faster.

Re: REST api for monitoring Spark Streaming

Thank you this should take me at least a few days, and will let you know as soon as the PR ready. On 11/8/16 11:44 AM, Tathagata Das wrote: This may be a good addition. I suggest you read our guidelines on contributing code to Spark.

Re: REST api for monitoring Spark Streaming

This may be a good addition. I suggest you read our guidelines on contributing code to Spark. https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-PreparingtoContributeCodeChanges Its long document but it should have everything for you to figure out how to

Re: REST api for monitoring Spark Streaming

hi everyone it seems that there is not much who interested in creating a api for Streaming. never the less I still really want the api for monitoring. so i tried to see if i can implement by my own. after some test, i believe i can achieve the goal by 1. implement a

Re: Handling questions in the mailing lists

Just a couple of random thoughts regarding Stack Overflow... * If we are thinking about shifting focus towards SO all attempts of micromanaging should be discarded right in the beginning. Especially things like meta tags, which are discouraged and "burninated"

Re: Spark Improvement Proposals

It turned out suggested edits (trackable) don't show up for non-owners, so I've just merged all the edits in place. It should be visible now. On Mon, Nov 7, 2016 at 10:10 AM, Reynold Xin wrote: > Oops. Let me try figure that out. > > > On Monday, November 7, 2016, Cody

Re: Spark Improvement Proposals

Oops. Let me try figure that out. On Monday, November 7, 2016, Cody Koeninger wrote: > 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

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: Handling questions in the mailing lists

Thanks Reynold for reviewing the ASF rules. Albeit the potential issues mentioned, I feel using StackOverflow would be a improvement. And yes, some guidelines/instructions have the potential to improve the questions and the "escalation" process. On 7 November 2016 at 10:48,

RE: Handling questions in the mailing lists

My two cents (As a user/consumer)… I have been following & using Spark in financial services before version 1 and before it migrated questions from Google Groups to apache mailing lists (which was a shame ☹ ). SO: There has been some momentum lately on SO, but as questions were not

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