+1 for planning EOL support for HBase 1.3, but can we do it after 4.16
release? I feel it because of the following reasons:-
(including user )
* It will be an advance notice to the users who have been waiting for fixes
in 4.16
release for a long time but are on HBase-1.3.
* As work is
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
