Response inline: On Tue, Mar 17, 2020 at 11:51 AM Tim Armstrong <tarmstr...@cloudera.com> wrote:
> I think I generally support this. A few specific comments. > > > Proposal 3: Impala-lzo > > Drop support for Impala-lzo/hadoop-lzo > > Does this mean dropping the plugin text scanner interface entirely? LZO is > the only implementation of that that I'm aware of (and we rely on it to > test the interface) so seems reasonable to me to remove something that has > minimal adoption and not cleanly separated from the scanner implementation > of core Impala. > I think it makes sense to make a clean break and remove the plugin text scanner interface unless there is a clear user. The interaction with the scanner side is unstable and intricate. I think this would be done immediately in Impala 4.0. > > > Proposal 5: Sentry > > Drop support for Sentry in favor of Ranger. > > I think moving this direction makes a lot of sense given that activity in > the Sentry project has declined a lot (just look at the activity level on > the two projects, it's dramatically different), unless someone in the > community wants to step up and maintain the integration. > > Proposal 6: Metadata > > Metadata V2 will become the default. Metadata V1 will be deprecated. > Maybe we should set a goal of removing the support in Impala 4.1 or 4.2? > That would allow us to remove a lot of complex code > I think it would be reasonable to decide that some version of Impala 4 will remove Metadata V1. The sooner the better, but it will depend on our assessment of V2. > > On Mon, Mar 16, 2020 at 10:07 AM Joe McDonnell <joemcdonn...@cloudera.com> > wrote: > > > Now that Impala 3.4 is branched and master is Impala 4.0, we need to > decide > > what breaking changes will happen in Impala 4.0. I have provided a series > > of proposals below. I welcome feedback on them. Other proposals are also > > welcome. > > > > Thanks, > > Joe > > > > Proposal 0: Hadoop component versions > > > > Switch to CDP versions of components by default. This means that Impala > > will use Hive 3+ (which is already essentially Hive 4 and may change > names > > to being Hive 4). > > Remove support for CDH versions of components. > > This was already discussed in the original thread for Impala 4, so this > is > > not new. > > > > Proposal 1: OS support > > > > Drop support for Centos 6, Ubuntu 14, and Debian (all versions) > > Retain support for Ubuntu 16, Ubuntu 18, Centos 7, and SLES 12 > > Centos 7 development will be focused on newer Centos 7 versions such as > 7.6 > > and 7.7. > > Add support for Centos 8 > > Move main development from Ubuntu 16 to Ubuntu 18 over time. > > > > Proposal 2: Python support > > > > Drop support for Python 2.6 > > Add support for Python 3 over time. > > > > Proposal 3: Impala-lzo > > > > Drop support for Impala-lzo/hadoop-lzo > > > > Proposal 4: Clients > > > > Deprecate beeswax protocol. This means that it can be removed in the next > > major version number, but it would not be removed in Impala 4. Current > > users of beeswax would need to start migrating to HS2. > > > > Proposal 5: Sentry > > > > Drop support for Sentry in favor of Ranger. > > > > Proposal 6: Metadata > > > > Metadata V2 will become the default. Metadata V1 will be deprecated. > > > > Thanks, > > Joe > > >
