[PHOENIX-5993] HBase 2.2.5 public maven artifacts are incompatible with Hadoop 3

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.0
• Component/s: core
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 07/Jul/20 07:55
• Updated: 31/Jul/20 07:05
• Resolved: 31/Jul/20 07:05

Description

The HBase artifacts downloadable from maven central are built with Hadoop 2.x

However, up to now, we could use these artifacts with Hadoop 3.0 and they worked. (Or we just didn't hit the incompatibilities in our test suite.)

This seems to have changed with 2.2.5, as the public maven artifact doesn't work with Hadoop 3.0.3 or 3.1.2 .

This is a known issue in HBase, and documented, but this means that

• Any client JAR we'd build with Hbase 2.2.5 would have the same problem.
• We cannot run our tests with Hbase 2.2.5

HBase's suggested solution is to rebuild HBase with the Hadoop version used in the cluster, and use that. This, however doesn't fit into our test or distribution process.

Issue Links

• is caused by: HBASE-22394 HdfsFileStatus incompatibility when used with Hadoop 3.1.x
• is related to: PHOENIX-6037 Change default HBase profile to 1.3 in 4.x
• relates to: OMID-163 Make Omid testable with HBase built for Hadoop3
• relates to: PHOENIX-5988 Bump HBase and Hadoop versions to latest working patch level on master
• relates to: PHOENIX-6016 Support HBase 2.3.0
• relates to: PHOENIX-6028 Change default HBase profile to 2.1 in 5.x