For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1519/
No changes
-1 overall
The following subsystems voted -1:
blanks hadolint pathlen spotbugs unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1323/
No changes
-1 overall
The following subsystems voted -1:
asflicense hadolint mvnsite pathlen unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/640/
No changes
-1 overall
The following subsystems voted -1:
blanks hadolint mvnsite pathlen spotbugs unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
+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
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
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
