Thanx Everyone. I think we have an agreement around dropping the Hbase v1
support.
I have created a ticket: https://issues.apache.org/jira/browse/HADOOP-19107
FYI. The HBase v2 build is broken now. I tried " mvn clean install
-DskipTests -Dhbase.profile=2.0" & it didn't work (It worked couple of
+1 for cutting hbase 1; it only reduces dependency pain (no more protobuf
2.5!)
Created the JIRA on that a few days back
https://issues.apache.org/jira/browse/YARN-11658
On Tue, 5 Mar 2024 at 12:08, Bryan Beaudreault
wrote:
> Hbase v1 is EOL for a while now, so option 2 probably makes sense.
+1 on supporting only HBase v2.
Masatake Iwasaki
On 2024/03/06 13:18, slfan1989 wrote:
+1 Option2
I also agree with the idea of upgrading hbase 2.2 to 2.5.
Shilun Fan.
Hbase v1 is EOL for a while now, so option 2 probably makes sense. While
you are at it you should probably update the
+1 Option2
I also agree with the idea of upgrading hbase 2.2 to 2.5.
Shilun Fan.
> Hbase v1 is EOL for a while now, so option 2 probably makes sense. While
> you are at it you should probably update the hbase2 version, because 2.2.x
> is also very old and EOL. 2.5.x is the currently maintained
Hbase v1 is EOL for a while now, so option 2 probably makes sense. While
you are at it you should probably update the hbase2 version, because 2.2.x
is also very old and EOL. 2.5.x is the currently maintained release for
hbase2, with 2.5.7 being the latest. We’re soon going to release 2.6.0 as
Hi Folks,
As of now we have two profiles for HBase: one for HBase v1(1.7.1) & other
for v2(2.2.4). The versions are specified over here: [1], how to build is
mentioned over here: [2]
As of now we by default run our Jenkins "only" for HBase v1, so we have
seen HBase v2 profile silently breaking a
