I will post 2.4.12RC0 tomorrow in fact.
On Thu, Apr 28, 2022 at 3:16 PM Josh Elser wrote:
> Definitely makes sense to drop 2.1 and 2.2 (which are long gone in
> upstream support).
>
> 2.3 isn't mentioned on HBase downloads.html anymore so I think that's
> also good to go, but 2.4 is still very
Definitely makes sense to drop 2.1 and 2.2 (which are long gone in
upstream support).
2.3 isn't mentioned on HBase downloads.html anymore so I think that's
also good to go, but 2.4 is still very much alive.
On 4/19/22 11:32 AM, Geoffrey Jacoby wrote:
+1 to dropping support for 2.1 and 2.2.
+1 to dropping support for 2.1 and 2.2.
Because of some incompatible 2.0-era changes to coprocessor interfaces, and
a bug around raw filters, we weren't able to support the newer global
indexes at all on 2.1, and even on 2.2 we have an issue where we can't
protect index consistency during major
We can also consider dropping support for 2.4.0.
On Tue, Apr 19, 2022 at 12:21 PM Istvan Toth wrote:
> Hi!
>
> Both Hbase 2.1 and 2.2 have been EOL for a little more than a year.
>
> Do we want to keep supporting them in HBase 5.2 ?
>
> Keeping them is not a big burden, as the compatibility
Hi!
Both Hbase 2.1 and 2.2 have been EOL for a little more than a year.
Do we want to keep supporting them in HBase 5.2 ?
Keeping them is not a big burden, as the compatibility modules are ready,
but we could simplify the compatibility module interface a bit, and free up
resources in the
