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" <[email protected]> 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 <[email protected]> >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 < >> [email protected]> 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 <[email protected]> >>> 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 >>> > >>> >> >>
