You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Philip Zeyliger <ph...@cloudera.com.INVALID> on 2018/06/15 18:23:06 UTC
Branch 2.x
Hi folks,
As you know, many of us have been maintaining the 2.x branch by having a
cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/)
and, when it fails, manually pushing through the issues. This has proven to
be quite the burden, and I'm planning on disabling the automatic job.
Please let this thread know if you're interested in adopting the 2.x
branch. If there are no takers, we can let it lie dormant.
Thanks!
-- Philip
Re:Re: Re: Branch 2.x
Posted by Quanlong Huang <hu...@126.com>.
Is it possible that we only apply bug fixes to the 2.x branch? Or can we wait until the master branch become healthy from broken/flasky tests and then cherry-pick all the bug fixes to the 2.x branch? It'd be great if we can at least release 2.13 so our works after 2.12 won't be wasted.
In addition, I think there're still guys (at least me) who volunteers to maintain the 2.x branch. Since not everyone in the Impala community (at least for those in the user mailing list) are informed about this breaking news, when they get this and find they can't upgrade to 3.x in short term, they may also join us to maintain the 2.x branch. The first step can be wait until the master branch become healthy and then catch up all the patches.
-- Quanlong
At 2018-06-23 05:14:39, "Philip Zeyliger" <ph...@cloudera.com.INVALID> wrote:
>Hi Quanlong,
>
>If someone wishes to step up and maintain the 2.x branch, they're very
>welcome to. To be transparent, some of the Cloudera employees are focusing
>considerably more on the 3.x line and aren't currently planning to release
>manage additional 2.x releases.
>
>On Wed, Jun 20, 2018 at 1:56 AM Quanlong Huang <hu...@126.com>
>wrote:
>
>> Sorry, Philip. Do you mean we won't apply new patches to the 2.x branch? I
>> thought you just mean to disable the automatic cherry-pick job.
>>
>>
>> In my limited understanding, there're two major breaking changes for the
>> 3.x branch:
>>
>>
>> * Standard SQL syntax: legacy HQL may fail on syntax errors in Impala-3.x
>> * Hadoop 3: Impala-3.x can only be deployed on Hadoop 3.x and Hive 2.x
>>
>
>If you run with IMPALA_MINICLUSTER_PROFILE=2, you should be able to
>continue to build and use against older versions of Hadoop. Taking support
>for that out is something we should do, but, frankly, it's a lot less of a
>pain to maintain. If you're planning on using this, it'd be useful to set
>up some more automated testing for it.
>
>Some of the SQL changes have flags to disable them (e.g., the reserved
>words list).
>
>Thanks,
>
>-- Philip
Re: Re: Branch 2.x
Posted by Philip Zeyliger <ph...@cloudera.com.INVALID>.
Hi Quanlong,
If someone wishes to step up and maintain the 2.x branch, they're very
welcome to. To be transparent, some of the Cloudera employees are focusing
considerably more on the 3.x line and aren't currently planning to release
manage additional 2.x releases.
On Wed, Jun 20, 2018 at 1:56 AM Quanlong Huang <hu...@126.com>
wrote:
> Sorry, Philip. Do you mean we won't apply new patches to the 2.x branch? I
> thought you just mean to disable the automatic cherry-pick job.
>
>
> In my limited understanding, there're two major breaking changes for the
> 3.x branch:
>
>
> * Standard SQL syntax: legacy HQL may fail on syntax errors in Impala-3.x
> * Hadoop 3: Impala-3.x can only be deployed on Hadoop 3.x and Hive 2.x
>
If you run with IMPALA_MINICLUSTER_PROFILE=2, you should be able to
continue to build and use against older versions of Hadoop. Taking support
for that out is something we should do, but, frankly, it's a lot less of a
pain to maintain. If you're planning on using this, it'd be useful to set
up some more automated testing for it.
Some of the SQL changes have flags to disable them (e.g., the reserved
words list).
Thanks,
-- Philip
Re:Re: Branch 2.x
Posted by Quanlong Huang <hu...@126.com>.
Sorry, Philip. Do you mean we won't apply new patches to the 2.x branch? I thought you just mean to disable the automatic cherry-pick job.
In my limited understanding, there're two major breaking changes for the 3.x branch:
* Standard SQL syntax: legacy HQL may fail on syntax errors in Impala-3.x
* Hadoop 3: Impala-3.x can only be deployed on Hadoop 3.x and Hive 2.x
If unfortunately you mean to abandon the 2.x branch, what should the users do if they can't upgrade their hadoop cluster? For a business-critical cluster whose data size reaches PB level, it's really hard for it to upgrade.
-- Quanlong
At 2018-06-19 03:18:40, "Tim Armstrong" <ta...@cloudera.com.INVALID> wrote:
>This just came up - do we want to backport bug or test fixes to 2.x or
>nothing at all?
>
>https://gerrit.cloudera.org/#/c/10722/
>
>On Mon, Jun 18, 2018 at 10:48 AM, Tim Armstrong <ta...@cloudera.com>
>wrote:
>
>> Thanks Phil, I think it will be good not to have to maintain this.
>>
>> On Mon, Jun 18, 2018 at 9:40 AM, Philip Zeyliger <
>> philip@cloudera.com.invalid> wrote:
>>
>>> I've not heard anything, so I've removed the "trigger" for job
>>> https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
>>> SCM" at an "@hourly" rate, looking for changes in asf/master.
>>>
>>> Thanks!
>>>
>>> -- Philip
>>>
>>> On Fri, Jun 15, 2018 at 11:23 AM Philip Zeyliger <ph...@cloudera.com>
>>> wrote:
>>>
>>> > Hi folks,
>>> >
>>> > As you know, many of us have been maintaining the 2.x branch by having a
>>> > cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/
>>> )
>>> > and, when it fails, manually pushing through the issues. This has
>>> proven to
>>> > be quite the burden, and I'm planning on disabling the automatic job.
>>> >
>>> > Please let this thread know if you're interested in adopting the 2.x
>>> > branch. If there are no takers, we can let it lie dormant.
>>> >
>>> > Thanks!
>>> >
>>> > -- Philip
>>> >
>>>
>>
>>
Re: Branch 2.x
Posted by Tim Armstrong <ta...@cloudera.com.INVALID>.
This just came up - do we want to backport bug or test fixes to 2.x or
nothing at all?
https://gerrit.cloudera.org/#/c/10722/
On Mon, Jun 18, 2018 at 10:48 AM, Tim Armstrong <ta...@cloudera.com>
wrote:
> Thanks Phil, I think it will be good not to have to maintain this.
>
> On Mon, Jun 18, 2018 at 9:40 AM, Philip Zeyliger <
> philip@cloudera.com.invalid> wrote:
>
>> I've not heard anything, so I've removed the "trigger" for job
>> https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
>> SCM" at an "@hourly" rate, looking for changes in asf/master.
>>
>> Thanks!
>>
>> -- Philip
>>
>> On Fri, Jun 15, 2018 at 11:23 AM Philip Zeyliger <ph...@cloudera.com>
>> wrote:
>>
>> > Hi folks,
>> >
>> > As you know, many of us have been maintaining the 2.x branch by having a
>> > cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/
>> )
>> > and, when it fails, manually pushing through the issues. This has
>> proven to
>> > be quite the burden, and I'm planning on disabling the automatic job.
>> >
>> > Please let this thread know if you're interested in adopting the 2.x
>> > branch. If there are no takers, we can let it lie dormant.
>> >
>> > Thanks!
>> >
>> > -- Philip
>> >
>>
>
>
Re: Branch 2.x
Posted by Tim Armstrong <ta...@cloudera.com.INVALID>.
Thanks Phil, I think it will be good not to have to maintain this.
On Mon, Jun 18, 2018 at 9:40 AM, Philip Zeyliger <
philip@cloudera.com.invalid> wrote:
> I've not heard anything, so I've removed the "trigger" for job
> https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
> SCM" at an "@hourly" rate, looking for changes in asf/master.
>
> Thanks!
>
> -- Philip
>
> On Fri, Jun 15, 2018 at 11:23 AM Philip Zeyliger <ph...@cloudera.com>
> wrote:
>
> > Hi folks,
> >
> > As you know, many of us have been maintaining the 2.x branch by having a
> > cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/)
> > and, when it fails, manually pushing through the issues. This has proven
> to
> > be quite the burden, and I'm planning on disabling the automatic job.
> >
> > Please let this thread know if you're interested in adopting the 2.x
> > branch. If there are no takers, we can let it lie dormant.
> >
> > Thanks!
> >
> > -- Philip
> >
>
Re: Branch 2.x
Posted by Philip Zeyliger <ph...@cloudera.com.INVALID>.
I've not heard anything, so I've removed the "trigger" for job
https://jenkins.impala.io/job/cherrypick-2.x-and-test/. It used to "Poll
SCM" at an "@hourly" rate, looking for changes in asf/master.
Thanks!
-- Philip
On Fri, Jun 15, 2018 at 11:23 AM Philip Zeyliger <ph...@cloudera.com>
wrote:
> Hi folks,
>
> As you know, many of us have been maintaining the 2.x branch by having a
> cherry-pick job (https://jenkins.impala.io/job/cherrypick-2.x-and-test/)
> and, when it fails, manually pushing through the issues. This has proven to
> be quite the burden, and I'm planning on disabling the automatic job.
>
> Please let this thread know if you're interested in adopting the 2.x
> branch. If there are no takers, we can let it lie dormant.
>
> Thanks!
>
> -- Philip
>