Re: Handling stale PRs

On Tue, Aug 26, 2014 at 2:02 AM, Patrick Wendell wrote: > it's actually precedurally difficult for us to close pull requests Just an FYI: Seems like the GitHub-sanctioned work-around to having issues-only permissions is to have a second, issues-only repository

Re: [VOTE] Release Apache Spark 1.1.0 (RC2)

Thanks to Nick Chammas and Cheng Lian who pointed out two issues with the release candidate. I'll cancel this in favor of RC3. On Fri, Aug 29, 2014 at 1:33 PM, Jeremy Freeman wrote: > +1. Validated several custom analysis pipelines on a private cluster in > standalone mode. Tested new PySpark sup

[VOTE] Release Apache Spark 1.1.0 (RC3)

Please vote on releasing the following candidate as Apache Spark version 1.1.0! The tag to be voted on is v1.1.0-rc3 (commit b2d0493b): https://git-wip-us.apache.org/repos/asf?p=spark.git;a=commit;h=b2d0493b223c5f98a593bb6d7372706cc02bebad The release files, including signatures, digests, etc. ca

[SPARK-3324] make yarn module as a unified maven jar project

Hi everyone! I found the YARN module has nonstandard path structure like: ${SPARK_HOME} |--yarn |--alpha (contains yarn api support for 0.23 and 2.0.x) |--stable (contains yarn api support for 2.2 and later) | |--pom.xml (spark-yarn) |--common (Common codes not depending

Fwd: Partitioning strategy changed in Spark 1.0.x?

Sending the response back to the dev list so this is indexable and searchable by others. -- Forwarded message -- From: Milos Nikolic Date: Sat, Aug 30, 2014 at 5:50 PM Subject: Re: Partitioning strategy changed in Spark 1.0.x? To: Reynold Xin Thank you, your insights were very