Hi Feri, Thanks for carefully considering this situation. I agree with your proposal that it is best to provide an HBase connector release with partial JDK support for the time being, and list the limitations in the Java compatibility docs.
On a partially related note this highlights that the community should consider investing into cleanly finishing the Java17 support, as this will continue to complicate efforts like yours. Thanks, Marton On Tue, Oct 22, 2024 at 1:47 PM Ferenc Csaky <ferenc.cs...@pm.me.invalid> wrote: > Hello devs, > > I would like to start a discussion regarding a new HBase connector > release. Currently, the > externalized HBase connector has only 1 release: 3.0.0 that supports Flink > 1.16 and 1.17. > > By stating this, it is obvious that the connector is already outdated for > quite a while. There > is a long-lasting ticket [1] to release a newer HBase version, which also > contains a major version > bump as HBase 1.x support is removed, but covering JDK17 with the current > Hadoop related > dependency mix is impossible, because there are parts that do not play > well with it when you > try to compile with JDK17+, and there are no runtime tests as well. > > Solving that properly will require to bump the HBase, Hadoop, and > Zookeeper versions as well, > but that will require more digging and some refactoring, at least on the > test side. > > To cut some corners and move forward I think at this point it would make > sense to release > version 4.0 that supports Flink 1.18 and 1.19 but only on top of JDK8 and > JDK11 just to close the > current gap a bit. I am thinking about including the limitations in the > java compat docs [2] to > highlight users. > > WDYT? > > Best, > Ferenc > > [1] https://issues.apache.org/jira/browse/FLINK-35136 > [2] > https://nightlies.apache.org/flink/flink-docs-release-1.19/docs/deployment/java_compatibility/
