Re: Timeline for Spark 2.3

hat.com>, dev <dev@spark.apache.org> > Date:2017/12/21 04:48 > Subject:Re: Timeline for Spark 2.3 > -- > > > > +1 > I think the earlier we cut a branch the better. > > -- > > *From:* Mi

Re: Timeline for Spark 2.3

Holden Karau <hol...@pigscanfly.ca> Cc: Sameer Agarwal <sam...@databricks.com>, Erik Erlandson <eerla...@redhat.com>, dev <dev@spark.apache.org> Date: 2017/12/21 04:48 Subject:Re: Timeline for Spark 2.3 +1 I think the earlier we cut a branch the be

Re: Timeline for Spark 2.3

+1 I think the earlier we cut a branch the better. From: Michael Armbrust <mich...@databricks.com> Sent: Tuesday, December 19, 2017 4:41:44 PM To: Holden Karau Cc: Sameer Agarwal; Erik Erlandson; dev Subject: Re: Timeline for Spark 2.3 Do people reall

Re: Timeline for Spark 2.3

Do people really need to be around for the branch cut (modulo the person cutting the branch)? 1st or 2nd doesn't really matter to me, but I am +1 kicking this off as soon as we enter the new year :) Michael On Tue, Dec 19, 2017 at 4:39 PM, Holden Karau wrote: > Sounds

Re: Timeline for Spark 2.3

Sounds reasonable, although I'd choose the 2nd perhaps just since lots of folks are off on the 1st? On Tue, Dec 19, 2017 at 4:36 PM, Sameer Agarwal wrote: > Let's aim for the 2.3 branch cut on 1st Jan and RC1 a week after that > (i.e., week of 8th Jan)? > > > On Fri, Dec

Re: Timeline for Spark 2.3

Let's aim for the 2.3 branch cut on 1st Jan and RC1 a week after that (i.e., week of 8th Jan)? On Fri, Dec 15, 2017 at 12:54 AM, Holden Karau wrote: > So personally I’d be in favour or pushing to early January, doing a > release over the holidays is a little rough with

Re: Timeline for Spark 2.3

So personally I’d be in favour or pushing to early January, doing a release over the holidays is a little rough with herding all of people to vote. On Thu, Dec 14, 2017 at 11:49 PM Erik Erlandson wrote: > I wanted to check in on the state of the 2.3 freeze schedule.

Re: Timeline for Spark 2.3

I wanted to check in on the state of the 2.3 freeze schedule. Original proposal was "late Dec", which is a bit open to interpretation. We are working to get some refactoring done on the integration testing for the Kubernetes back-end in preparation for testing upcoming release candidates,

Re: Timeline for Spark 2.3

Hi, What is the process to request an issue/fix to be included in the next release? Is there a place to vote for features? I am interested in https://issues.apache.org/jira/browse/SPARK-13127, to see if we can get Spark upgrade parquet to 1.9.0, which addresses the

Re: Timeline for Spark 2.3

Sounds good to me too. In addition to what has already been pointed out about the Spark History Server and the Kubernetes support, this would also give us enough time to further polish the new data source v2 API and the vectorized UDF API to iron out any kinks. I'd like to volunteer to serve as

Re: Timeline for Spark 2.3

I would love too to have SPARK-18016. I think it would help a lot of users. 2017-11-10 5:58 GMT+01:00 Nick Pentreath : > +1 I think that’s practical > > On Fri, 10 Nov 2017 at 03:13, Erik Erlandson wrote: > >> +1 on extending the deadline. It will

Re: Timeline for Spark 2.3

+1 I think that’s practical On Fri, 10 Nov 2017 at 03:13, Erik Erlandson wrote: > +1 on extending the deadline. It will significantly improve the logistics > for upstreaming the Kubernetes back-end. Also agreed, on the general > realities of reduced bandwidth over the

Re: Timeline for Spark 2.3

+1 on extending the deadline. It will significantly improve the logistics for upstreaming the Kubernetes back-end. Also agreed, on the general realities of reduced bandwidth over the Nov-Dec holiday season. Erik On Thu, Nov 9, 2017 at 6:03 PM, Matei Zaharia wrote: >

Re: Timeline for Spark 2.3

I’m also +1 on extending this to get Kubernetes and other features in. Matei > On Nov 9, 2017, at 4:04 PM, Anirudh Ramanathan > wrote: > > This would help the community on the Kubernetes effort quite a bit - giving > us additional time for reviews and testing for

Re: Timeline for Spark 2.3

This would help the community on the Kubernetes effort quite a bit - giving us additional time for reviews and testing for the 2.3 release. On Thu, Nov 9, 2017 at 3:56 PM, Justin Miller wrote: > That sounds fine to me. I’m hoping that this ticket can make it into

Re: Timeline for Spark 2.3

That sounds fine to me. I’m hoping that this ticket can make it into Spark 2.3: https://issues.apache.org/jira/browse/SPARK-18016 It’s causing some pretty considerable problems when we alter the columns to be nullable, but we are OK for now

Timeline for Spark 2.3

According to the timeline posted on the website, we are nearing branch cut for Spark 2.3. I'd like to propose pushing this out towards mid to late December for a couple of reasons and would like to hear what people think. 1. I've done release management during the Thanksgiving / Christmas time