+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 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
well.
On Tue, Mar 5, 2024 at 6:56 AM Ayush Saxena wrote:
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 couple of times.
Considering there are stable versions for HBase v2 as per [3] & HBase v2
seems not too new, I have some suggestions, we can consider:
* Make HBase v2 profile as the default profile & let HBase v1 profile stay
in our code.
* Ditch HBase v1 profile & just lets support HBase v2 profile.
* Let everything stay as is, just add a Jenkins job/ Github action which
compiles HBase v2 as well, so we make sure no change breaks it.
Personally I would go with the second option, the last HBase v1 release
seems to be 2 years back, it might be pulling in some
problematic transitive dependencies & it will open scope for us to support
HBase 3.x when they have a stable release in future.
Let me know your thoughts!!!
-Ayush
[1]
https://github.com/apache/hadoop/blob/dae871e3e0783e1fe6ea09131c3f4650abfa8a1d/hadoop-project/pom.xml#L206-L207
[2]
https://github.com/apache/hadoop/blob/dae871e3e0783e1fe6ea09131c3f4650abfa8a1d/BUILDING.txt#L168-L172
[3] https://hbase.apache.org/downloads.html
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
