Re: How do a new developer create or assign a jira ticket?

Thanks Holden, Will check out! Neil On Wednesday, July 27, 2016, Holden Karau wrote: > Hi Neil, > > Thanks for your interest in participating in Apache Spark! You can create > JIRAs - but first you will need to signup for an Apache JIRA account. > Generally we can't

Re: How do a new developer create or assign a jira ticket?

Hi Neil, Thanks for your interest in participating in Apache Spark! You can create JIRAs - but first you will need to signup for an Apache JIRA account. Generally we can't assign JIRAs to ourselves - but you can leave a comment saying your interested in working. I think for R a good place to get

Apply patch to 1.2.1.spark2

Hi, Is there a way to apply this patch to ?

Re: [build system] jenkins downtime friday afternoon, july 29th 2016

reminder -- this is happening friday afternoon. i will pause the build queue late friday morning. On Mon, Jul 25, 2016 at 2:29 PM, shane knapp wrote: > around 1pm friday, july 29th, we will be taking jenkins down for a > rack move and celebrating national systems

Re: Internal Deprecation warnings - worth fixing?

Great it sounds like is a general consensus that these are worth fixing so I'll start tackling some of these so we can hopefully get down to the point that we will notice new warnings and be able to consider them. On Wed, Jul 27, 2016 at 4:11 PM, Sean Owen wrote: > Yeah I

Re: Internal Deprecation warnings - worth fixing?

Yeah I tried to zap lots of those before the release, but there are still many of them, mostly from the accumulator change (really, that should have been fixed as part of the original change? not so nice to merge a change that adds 200 build warnings). Some deprecated code must be called from

Re: Internal Deprecation warnings - worth fixing?

+1 for fixing :) Dongjoon. On Wed, Jul 27, 2016 at 12:53 PM, Nick Pentreath wrote: > +1 I don't believe there's any reason for the warnings to still be there > except for available dev time & focus :) > > On Wed, 27 Jul 2016 at 21:35, Jacek Laskowski

Re: Internal Deprecation warnings - worth fixing?

+1 I don't believe there's any reason for the warnings to still be there except for available dev time & focus :) On Wed, 27 Jul 2016 at 21:35, Jacek Laskowski wrote: > Kill 'em all -- one by one slowly yet gradually! :) > > Pozdrawiam, > Jacek Laskowski > >

Re: Internal Deprecation warnings - worth fixing?

Kill 'em all -- one by one slowly yet gradually! :) Pozdrawiam, Jacek Laskowski https://medium.com/@jaceklaskowski/ Mastering Apache Spark http://bit.ly/mastering-apache-spark Follow me at https://twitter.com/jaceklaskowski On Wed, Jul 27, 2016 at 9:11 PM, Holden Karau

Internal Deprecation warnings - worth fixing?

Now that the 2.0 release is out the door and I've got some cycles to do some cleanups - I'd like to know what other people think of the internal deprecation warnings we've introduced in a lot of a places in our code. Once before I did some minor refactoring so the Python code which had to use the

tpcds for spark2.0

hi,all: I want to have a test about tpcds99 sql run on spark2.0. I user https://github.com/databricks/spark-sql-perf about the master version ,when I run :val tpcds = new TPCDS (sqlContext = sqlContext) I got error: scala> val tpcds = new TPCDS (sqlContext = sqlContext) error: missing or invalid

Re: [ANNOUNCE] Announcing Apache Spark 2.0.0

Hold the release! There is a minor documentation issue :) But seriously, congrats all on this massive achievement! Anyway, I think it would be very helpful to add a link to the Structured Streaming Developer Guide (Alpha) to both the documentation home page and from the beginning of the "old"

[ANNOUNCE] Announcing Apache Spark 2.0.0

Hi all, Apache Spark 2.0.0 is the first release of Spark 2.x line. It includes 2500+ patches from 300+ contributors. To download Spark 2.0, head over to the download page: http://spark.apache.org/downloads.html To view the release notes: http://spark.apache.org/releases/spark-release-2-0-0.html