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" <bikramjeet....@cloudera.com.INVALID> wrote: >+1 on removing it. > >On Wed, Jul 11, 2018 at 10:49 AM, Philip Zeyliger < >phi...@cloudera.com.invalid> wrote: > >> I'm +1 on removing it. >> >> On Wed, Jul 11, 2018 at 9:39 AM Sailesh Mukil <sail...@cloudera.com.invalid >> > >> 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 >> <fwij...@cloudera.com.invalid >> > > >> > 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? >> > > >> > >>
