Hey, Mohsen The highest supported Flink version is 1.20 in Flink CDC, and this Flink version uses JDK8 by default, but Debezium 2+ requires JDK11 at least, That’s why the Debezium version bump task is stale. IMO, once Flink CDC’s lowest supported Flink version becomes 2.0(which uses JDK11), it’s time to upgrade Debezium version, maybe we need two minor versions to achieve JDK8 support deprecation.
We don’t need a FLIP to upgrade a dependency version usually, except the version bump would break Flink CDC’ API compatibility, this follows Flink project’s bylaw as well. Feel free to take FLINK-36605 if you’d like to contribute this. Best, Leonard > 2025 6月 17 02:03，Mohsen Rezaei <morezae...@gmail.com> 写道： > > Hi devs, > > As we're upgrading the Flink CDC component, I'd like to turn some attention > to the version of debezium supported by the component [1]. This is one > major version behind the earliest tested Debezium version [2] reported by > Debezium, and two major versions behind the latest stable [3]. > > I noticed an issue [4] reported on this already, but with no activity, and > I wanted to ask how can we get Flink CDC upgraded to the latest stable > version, i.e. FLIP, etc.? Is this a priority/bandwidth issue, or a general > compatibility problem with the rest of the Flink ecosystem? > > Thanks, > Mohsen > > [1] https://debezium.io/releases/1.9/ > [2] https://debezium.io/releases/2.7/ > [3] https://debezium.io/releases/3.1/ > [4] https://issues.apache.org/jira/browse/FLINK-36605
