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