Hi Joao, Thanks for bringing up this topic! I think in general it's a pattern that connectors a lagging behind a bit. I think the community could use some help in general on this front.
For the specifics you mentioned I think the Kafka connector is in a fairly good place to cut a new version of it with Flink 2.1 and 2.2 support. I'm happy to help with that and volunteer as release manager. AFAIK on the CDC front, there is a lot of required changes to make it Flink 2.x compatible, and the original plan was that the next release will support Flink 2 that will come around the end of Feb, but it was pushed back to the subsequent release. If there is someone who has more info on JDBC feel free to chime in, but I'm happy to target that after the Kafka connector. Although I need to look things up for that connector, cause I'm not really up-to-date there. Best, Ferenc On Wednesday, February 11th, 2026 at 09:36, Joao Boto <[email protected]> wrote: > Hi all, > > I’ve noticed that several key connectors are currently lagging behind the > Flink release cycle. While Flink is already pushing toward version 2.3, > many connectors seem to be stuck at version 2.0 compatibility. > > This creates a support gap: since Flink officially supports the two most > recent versions, these connectors risk falling into unsupported territory. > In this scenario, it almost feels safer to stay on a 1.20-compatible > version given its LTS status. > > Is there a roadmap to align the following connectors more closely with the > latest Flink releases? > > - > > *flink-connector-kafka* > - > > *flink-connector-jdbc* > - > > *flink-cdc* (currently limited to 1.20) > > Any insight into the maintenance plan for these would be greatly > appreciated. > > Best regards >
