Hi Gunnar,

I checked the Debezium releases overview sheet [1], and it seems the latest 
Debezium 3.x requires at least Java 17. As the next CDC version is expected to 
be based on Flink 2.x that still supports Java 11 [2], is it reasonable to keep 
the same JDK requirement?

The highest version that still supports Java 11 is Debezium 2.7, and it could 
be progressively upgraded to 3.x until we dropped Java 11 support eventually. 
WDYT?

[1] https://debezium.io/releases/
[2] 
https://nightlies.apache.org/flink/flink-docs-stable/docs/try-flink/local_installation/

Best Regards,
Xiqian

2025年11月4日 00:22,Gunnar Morling <[email protected]> 写道:

Which version of Debezium would this be upgrading to?

I'd very much recommend going to the current 3.x, it has so many new
features and bug fixes compared to 1.9.x.

Best,

--Gunnar


On Mon, 3 Nov 2025 at 15:27, ConradJam <[email protected]> wrote:

Thank you for pushing forward. If it involves debezium version updates and
Flink cross version updates, would it be better to use Flink-cdc-4.0
version number? By the way, to which version will debezium be updated

Xiqian YU <[email protected]> 于2025年11月3日周一 10:01写道:

+1, thanks Kunni for driving this major release!

Best Regards,
Xiqian

2025年10月31日 17:40,Leonard Xu <[email protected]> 写道:

+1 for the proposal and release manager candidate.

And I’m looking forward to the support with ongoing Flink 2.2 version.

Best,
Leonard

2025 10月 31 15:22,Yanquan Lv <[email protected]> 写道:

Hi devs,

As Flink CDC 3.5 was released recently, it's a good time to kick off
the
upcoming Flink CDC 3.6 release cycle.

For a long time, we have received significant feedback from community
users
regarding the need to upgrade Flink/Debezium version dependencies. We
plan
to gradually address these requests in the upcoming releases.
Moreover,
as
the framework's capabilities continue to enhance, we will devote more
effort to providing more robust connectors.

In this version, we will focus on the following development tasks:

1. Upgrade the Flink dependency to version 2.2 and integrate new
features from the higher Flink version. This involves adding FLIP-27
API-based implementations to the current TiDB and Vitess connectors,
which
are currently implemented using the SourceFunction interface.
2. Add synchronized schema evolution support to the PostgreSQL
Pipeline
connector and introduce a new Kafka Pipeline Source connector, which
has
been frequently reported by users.
3.  Add support for LanceDB/Milvus pipeline connectors and explore
YAML-based configuration for RAG scenarios.

For developers who are interested in participating and contributing
new
features in this release cycle, please feel free to create a task that
targets cdc-3.6.0 to trace your planning features [1].

I'm happy to volunteer as a release manager and of course open to work
together with someone on this.
To ensure that we can complete the above plan, we plan to complete the
development of Flink CDC 3.6 in 2026-02-28.


Best,
Yanquan

[1]


https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20component%20%3D%20%22Flink%20CDC%22





Reply via email to