The HBase community has just unanimously EOLed HBase 1.3.

As I recall, 1.3 has some significant differences with 1.4+ that we have to
workaround via compatibility shim, particularly with metrics and changes to
the HBase Scan API. (In particular, the scan API changes are difficult to
handle even with the shim.)

Should we simplify our 4.x branch by removing 1.3 support for the upcoming
4.16 release?

Geoffrey

Reply via email to