+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? > > > > > >
