Re: KEYS file?

Aha, that's landed. OK I'll figure it out tomorrow and push my update to verify it all works. On Mon, Jul 11, 2016 at 8:54 PM, Reynold Xin wrote: > It's related to this apparently: > https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-12055 >

Re: KEYS file?

Eh, to anyone else who's ever pushed to the SVN-hosted spark.apache.org site: are you able to commit anything right now? This error is brand-new and has stumped me: svn: E195023: Changing file '/Users/srowen/Documents/asf-spark-site/downloads.md' is forbidden by the server svn: E175013: Access to

Re: branch-2.0 is now 2.0.1-SNAPSHOT?

I just bumped master branch version to 2.1.0-SNAPSHOT https://github.com/apache/spark/commit/ffcb6e055a28f36208ed058a42df09c154555332 We used to have a problem with binary compatibility check not having the 2.0.0 base version in Maven (because 2.0.0 hasn't been released yet) but I figured out a

Re: Spark 2.0.0 performance; potential large Spark core regression

Ted, That bug was https://issues.apache.org/jira/browse/SPARK-15822 and only found as part of running an sql-flights application (not with the unit tests), I don't know if this has anything to do with the regression we're seeing One update is that we see the same ballpark regression for 1.6.2

Re: Spark performance regression test suite

Agreed, this is something that we do regularly when producing our own Spark distributions in IBM and so it will be beneficial to share updates with the wider community, so far it looks like Spark 1.6.2 is the best out of the box on spark-perf and HiBench (of course this may vary for real

Re: Spark performance regression test suite

I second any effort to update, automate, and communicate the results of spark-perf (https://github.com/databricks/spark-perf) On Fri, Jul 8, 2016 at 12:28 PM, Eric Liang wrote: > Something like speed.pypy.org >

Re: Stability of branch-2.0

I agree -- Wenchen/Reynold do you know what's the theory there? TBH I think that there has not been a 'real' release candidate yet. It's not that big a deal if these first two have been speculative RCs to get more feedback earlier for a major release, and that in fact people want to let this bake

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

Yeah there were already other blockers when the RC was released. This one was already noted in this thread. There will another RC soon I'm sure. I guess it would be ideal if the remaining blockers were resolved one way or the other before that, to make it possible that RC3 could be the final

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

-1 https://issues.apache.org/jira/browse/SPARK-16379 > On Jul 6, 2016, at 19:28, Maciej Bryński wrote: > > -1 > https://issues.apache.org/jira/browse/SPARK-16379 >

Stability of branch-2.0

It looks like the vote on 2.0-rc2 will not pass so there will be a new RC from the 2.0 branch. With a project management hat on I would expect to see only fixes to the remaining blocker issues or high priority bug fixes going into the 2.0 branch as defect burn down. However, I see several new

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

Sorry for bringing this topic up. Any updates here? Really looking forward to the upcoming RC. Thanks! On Wed, Jul 6, 2016 at 6:19 PM, Ted Yu wrote: > Running the following command: > build/mvn clean -Phive -Phive-thriftserver -Pyarn -Phadoop-2.6 -Psparkr >

Re: branch-2.0 is now 2.0.1-SNAPSHOT?

You are right, this is messed up a bit now. branch-2.0 should really still be 2.0.0-SNAPSHOT, technically. I think that was accidentally updated in the RC release. It won't matter a whole lot except for people who consume snapshots, but, you can always roll your own. After 2.0.0 it should be

SPARK-15465 - AnalysisException: cannot cast StructType to VectorUDT

Hi! I want to bring this issue of Spark 2.0 here https://issues.apache.org/jira/browse/SPARK-15465. It looks quite major (I would even say critical) to me. Should it be fixed within RC? I would also like to contribute myself but struggle to find a place where to start... Thanks! -- Dmitry