impala-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Apple <jbap...@cloudera.com>
Subject Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Date Tue, 12 Dec 2017 19:11:50 GMT
If this is high priority, do you want to start 3.0 planning?

On Tue, Dec 12, 2017 at 11:09 AM, Alexander Behm <alex.behm@cloudera.com>
wrote:

> Of course there's always the option of committing to master and then
> reverting it in point-release branches, but that means we'll need to not
> forget to do that.
>
> On Tue, Dec 12, 2017 at 11:03 AM, Alexander Behm <alex.behm@cloudera.com>
> wrote:
>
> > I meant doing it in a point release.
> >
> > On Tue, Dec 12, 2017 at 11:02 AM, Dimitris Tsirogiannis <
> > dtsirogiannis@cloudera.com> wrote:
> >
> >> I think this is a good idea. Maybe we should do it in the next major
> >> release (v3) instead of a point release, unless that's what you meant.
> >>
> >> Dimitris
> >>
> >> On Tue, Dec 12, 2017 at 10:57 AM, Alexander Behm <
> alex.behm@cloudera.com>
> >> wrote:
> >>
> >>> Reserving standard SQL keywords seems like a reasonable thing to do,
> but
> >>> it
> >>> is an incompatible change. I think it should be ok to include the
> change
> >>> in
> >>> the next Impala release (whatever comes after 2.11), but wanted to hear
> >>> other opinions.
> >>>
> >>> See:
> >>> https://issues.apache.org/jira/browse/IMPALA-3916
> >>>
> >>
> >>
> >
>

Mime
View raw message