Re: [VOTE] SPARK 2.3.2 (RC3)

2018-07-29 Thread Xiao Li
Sounds good to me. Thanks! Today, we merged another correctness fix https://github.com/apache/spark/pull/21772. Xiao 2018-07-29 18:31 GMT-07:00 Saisai Shao : > Sure, I will do a next RC. I'm still waiting for a CVE fix, if this can be > done in this two days, I will also include that one. > > Xi

Re: [VOTE] SPARK 2.3.2 (RC3)

2018-07-29 Thread Saisai Shao
Sure, I will do a next RC. I'm still waiting for a CVE fix, if this can be done in this two days, I will also include that one. Xiao Li 于2018年7月28日周六 上午12:05写道: > The following blocker/important fixes have been merged to Spark 2.3 branch: > > https://issues.apache.org/jira/browse/SPARK-24927 > h

Re: code freeze and branch cut for Apache Spark 2.4

2018-07-29 Thread Holden Karau
I’m excited to have more folks rotate through release manager :) On Sun, Jul 29, 2018 at 3:57 PM Stavros Kontopoulos < stavros.kontopou...@lightbend.com> wrote: > +1. That would great! > > Thanks, > Stavros > > On Sun, Jul 29, 2018 at 5:05 PM, Wenchen Fan wrote: > >> If no one objects, how about

Re: code freeze and branch cut for Apache Spark 2.4

2018-07-29 Thread Stavros Kontopoulos
+1. That would great! Thanks, Stavros On Sun, Jul 29, 2018 at 5:05 PM, Wenchen Fan wrote: > If no one objects, how about we make the code freeze one week later(Aug > 8th)? > > BTW I'd like to volunteer to serve as the release manager for Spark 2.4. > I'm familiar with most of the major features

Re: [DISCUSS] Multiple catalog support

2018-07-29 Thread Ryan Blue
Wenchen, what I'm suggesting is a bit of both of your proposals. I think that USING should be optional like your first option. USING (or format(...) in the DF side) should configure the source or implementation, while the catalog should be part of the table identifier. They serve two different pur

Re: code freeze and branch cut for Apache Spark 2.4

2018-07-29 Thread Wenchen Fan
If no one objects, how about we make the code freeze one week later(Aug 8th)? BTW I'd like to volunteer to serve as the release manager for Spark 2.4. I'm familiar with most of the major features targeted for the 2.4 release. I also have a lot of free time during this release timeframe and should

Re: [Spark SQL] Future of CalendarInterval

2018-07-29 Thread Daniel Mateus Pires
Sounds good! @Xiao @Reynold AFAIK the only data type that is valid to cast to Calendar Interval is VARCHAR here is Postgres: postgres=# select CAST(CAST(interval '1 hour' AS varchar) AS interval); interval -- 01:00:00 (1 row) (snippet comes from the JIRA) Thanks, Daniel On 27 July