The tricky thing about backporting all bug-fixes is that 41 of the 91 resolved issues in the past four weeks are bugs:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20%3D%20Fixed%20AND%20resolved%20%3E%3D%20-4w%20ORDER%20BY%20issuetype%20DESC%2C%20created%20DESC Backporting all of them could be substantial labor requiring the dedicated attention of a committer. That said, not all of those JIRAs are correctly typed (some may be improvements), and it might be possible to backport a most critical subset to 2.x without heavy commitment from a committer as long as someone, committer or not takes the lead. On Wed, Jul 11, 2018 at 5:55 PM, Quanlong Huang <[email protected]> wrote: > So there're no more official supports for Hadoop 2, even for bug-fix? I > know the master branch may have only support Hadoop 3 with full test > coverage now. But I don't identify with you to abandon users in Hadoop 2. > What if they encounter a critical bug in impala-2.12 and can not upgrade > their heavy cluster to Hadoop3? > > > I'm +1 for this if we can bring 2.x branch back to live even we only patch > bug-fixes on it. > > At 2018-07-12 02:31:44, "Bikramjeet Vig" <[email protected]> > wrote: > >+1 on removing it. > > > >On Wed, Jul 11, 2018 at 10:49 AM, Philip Zeyliger < > >[email protected]> wrote: > > > >> I'm +1 on removing it. > >> > >> On Wed, Jul 11, 2018 at 9:39 AM Sailesh Mukil > <[email protected] > >> > > >> wrote: > >> > >> > +1 for removing it. > >> > > >> > I'm all for reduced complexity if not a lot of users are benefitting > from > >> > it. > >> > > >> > On Wed, Jul 11, 2018 at 9:29 AM, Fredy Wijaya > >> <[email protected] > >> > > > >> > wrote: > >> > > >> > > Hi all, > >> > > > >> > > In the master branch, we support both Hadoop 2 and Hadoop 3 via > >> > > IMPALA_MINICLUSTER_PROFILE environment variable. When Impala > >> transitioned > >> > > from Hadoop 2 to Hadoop 3, we introduced IMPALA_MINICLUSTER_PROFILE > as > >> a > >> > > way to easily switch between Hadoop 2 and Hadoop 3. It made sense at > >> that > >> > > time. However, I believe the IMPALA_MINICLUSTER_PROFILE=2 has > outlived > >> > its > >> > > usefulness and has grown more complex to maintain given that we > need to > >> > > introduce shims, feature flags, additional Jenkins jobs, etc. Given > >> that > >> > we > >> > > already have 2.x branch for Impala with Hadoop 2 support. I'm > proposing > >> > > that we remove IMPALA_MINICLUSTER_PROFILE=2 in the master branch so > >> that > >> > we > >> > > can focus our effort on supporting Hadoop 3 on the master branch. > >> > > > >> > > What do others think? > >> > > > >> > > >> >
