Hi Xiqian, So what does this change entail? Does it just involve changing the debezium version in our POM xml?
Thanks Sachin On Tue, May 26, 2026 at 9:46 AM Xiqian YU <[email protected]> wrote: > Hi Sachin, > > Currently, Flink CDC still uses Debezium 1.9.8.Final with various > backported patches, most of them are monkey-patched files located in the > `io.debezium` package. We were stuck at 1.x for a long time because > Debezium 2.0+ requires at least Java 11. > > There is an open JIRA ticket, FLINK-36605 [1], aiming to upgrade Debezium > to 2.7. As FLINK-38730 [2] has dropped Flink CDC's Java 8 support, this > ticket seems doable now. > > Best Regards, > Xiqian > > [1] https://issues.apache.org/jira/browse/FLINK-36605 > [2] https://issues.apache.org/jira/browse/FLINK-38730 > > > Sachin Mittal <[email protected]> 於 2026年5月25日 22:57 寫道： > > > > Hi, > > I was checking the Flink CDC release 3.6 and I see that it is using the > debezium core version on 1.9. > > However when I check the debezium release, it has a stable release > version of 3.5. > > Why is there such a huge gap? > > > > The problem I am facing is that for Oracle CDC I am getting PGA limit > exceeded exception many times and some analysis has suggested moving to a > latest debezium release as they had fixed on how logminer is read in their > later versions. > > > > Can someone from the Flink CDC team or developer comment on the same ? > > > > Thanks > > Sachin > > > >
