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 months back IIRC), Some sl4j exclusion needs to be added I believe Maybe an upgrade of the HBase v2 version might solve it, if not we need to handle it in our code. We can chase the upgrade of v2 version as Bryan mentioned either in a different ticket parallely or together with this as well :-) In case anyone has objections/suggestions do shout out here or on the ticket or both -Ayush On Mon, 11 Mar 2024 at 19:22, Steve Loughran <ste...@cloudera.com.invalid> wrote: > +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 <bbeaudrea...@apache.org> > wrote: > > > 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 <ayush...@gmail.com> 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 > > > > > >
