You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by Alexander Behm <al...@cloudera.com> on 2017/12/12 18:57:12 UTC
Reserving standard SQL keywords next Impala release (IMPALA-3916)
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
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Jim Apple <jb...@cloudera.com>.
If this is high priority, do you want to start 3.0 planning?
On Tue, Dec 12, 2017 at 11:09 AM, Alexander Behm <al...@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 <al...@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
> >>>
> >>
> >>
> >
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Jim Apple <jb...@cloudera.com>.
If this is high priority, do you want to start 3.0 planning?
On Tue, Dec 12, 2017 at 11:09 AM, Alexander Behm <al...@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 <al...@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
> >>>
> >>
> >>
> >
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Alexander Behm <al...@cloudera.com>.
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 <al...@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 <al...@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
>>>
>>
>>
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Alexander Behm <al...@cloudera.com>.
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 <al...@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 <al...@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
>>>
>>
>>
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Alexander Behm <al...@cloudera.com>.
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 <al...@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
>>
>
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Alexander Behm <al...@cloudera.com>.
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 <al...@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
>>
>
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Dimitris Tsirogiannis <dt...@cloudera.com>.
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 <al...@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
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Jim Apple <jb...@cloudera.com>.
I'd prefer to wait until 3.0 for the sake of users, especially ones who use
Impala through other tools that might get quoting wrong.
On Tue, Dec 12, 2017 at 10:57 AM, Alexander Behm <al...@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
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Dimitris Tsirogiannis <dt...@cloudera.com>.
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 <al...@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
>
Re: Reserving standard SQL keywords next Impala release (IMPALA-3916)
Posted by Jim Apple <jb...@cloudera.com>.
I'd prefer to wait until 3.0 for the sake of users, especially ones who use
Impala through other tools that might get quoting wrong.
On Tue, Dec 12, 2017 at 10:57 AM, Alexander Behm <al...@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
>