---
> From: Sean Busbey
> Sent: Thursday, May 30, 2019 9:06 AM
> To: user@hbase.apache.org
> Cc: dev
> Subject: Re: [DISCUSS] Publishing hbase binaries with different hadoop
> release lines
>
>
> What about moving back to having a per-major-version-of-hadoop
> compati
he API can be versioned along with hbase as a
separate artifact.
-Original Message-
From: Sean Busbey
Sent: Thursday, May 30, 2019 9:06 AM
To: user@hbase.apache.org
Cc: dev
Subject: Re: [DISCUSS] Publishing hbase binaries with different hadoop release
lines
What about moving back to having a
What about moving back to having a per-major-version-of-hadoop
compatibility module again that builds against one needed major version all
the time? (Presumably with some shell script magic to pick the right one?)
that would be preferable imho to e.g. producing main project binary
tarballs per
I can't comment whether we need every Hadoop release but at the minimum,
2.8.5 as we recently switched to it from 2.7.7. I ran into issues with
2.8.5 and 2.1.5rc0 and used workaround in
https://issues.apache.org/jira/browse/HBASE-22052 to overcome it. I guess
if 2.1 will not live past 2.1.6 then
See the comments here
https://issues.apache.org/jira/browse/HBASE-22394
Although we claim that hbase 2.1.x can work together with hadoop 3.1.x,
actually we require users to build the hbase binary with hadoop 3.1.x by
their own if they really want to use hbase together with hadoop 3.1.x
clients.
