[Feature][Connector-V2] Upgrade Debezium to 2.7.4.Final

[vsantonastaso]

Search before asking

• I had searched in the feature and found no similar feature requirement.

Description

Context

Seatunnel is currently on Debezium 1.9.8.
This is the first step toward upgrading to the latest version (3.x).
Jumping directly from 1.9.8 to 3.x is too risky, so we're doing this in iteration.
This issue covers upgrading to 2.7.4.Final (latest 2.x LTS release).

Related: #10632

Why 2.7.4.Final?

• It's the latest stable 2.x release
• More conservative upgrade path from 1.9.8

Once this is stable, we can plan the 3.x upgrade separately.

Affected Components

• MySQL CDC connector
• Oracle CDC connector
• PostgreSQL CDC connector
• SQL Server CDC connector

Compatibility Notes

Debezium 2.x should still support MySQL 5.7 but it's not fully tested for this version, so we need to verify this during testing. If there are issues, we'll document and discuss them before merging.

Next Steps

After this merges and stabilizes, we can open a separate issue for the 3.x upgrade.

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[davidzollo]

Thanks for raising this. I agree the upgrade is valuable, but this is larger than a normal dependency bump.

In SeaTunnel’s CDC modules we do not only depend on Debezium externally; we also carry a number of copied / customized io.debezium classes across MySQL, Postgres, SQL Server, Oracle and others. So the real work here is compatibility migration, not just changing a Maven version.

My suggestion would be:

1. first identify the affected connectors and copied classes
2. define a phased upgrade plan
3. validate connector-by-connector instead of attempting one huge all-in PR

That will make the work much safer and much easier to review.

[DanielLeens]

Thanks for raising this. I checked the current repository state again: Debezium is still pinned at 1.9.8.Final in the core CDC dependency path, and some CDC connectors still depend on copied / customized Debezium internals.

So I agree this upgrade is worth doing, but I would not treat it as a simple dependency bump. I also do not see a dev PR linked to this issue yet. The safest next step is to keep this as the umbrella issue and split the real work connector by connector, starting with the lower-risk paths first.

[davidzollo]

@vsantonastaso I think you can have a try!

[DanielLeens]

Thanks, and I agree with keeping this moving.

I re-checked the current repository state on dev: Debezium is still pinned at 1.9.8.Final, and this is not only an external dependency bump for SeaTunnel. We still carry copied / customized io.debezium classes in several CDC modules, so the real work here is compatibility migration.

So from the current code base, the safest next step is:

1. keep this issue as the umbrella tracker
2. open a focused PR against dev
3. keep that PR scoped to Debezium 2.7.4.Final only
4. clearly list the affected connectors / copied classes in the PR description

I still do not see a dev PR linked here yet, so the next concrete milestone is to get that first reviewable slice opened. A smaller connector-by-connector path will be much easier to validate than one large all-in change.

[julianbradford19-png]

Thanks for the guidance, Daniel and David. I’ll start with a small PR targeting Debezium 2.7.4.Final for one connector first and list all affected copied classes.

…

On Wed, Apr 8, 2026, 2:53 AM Daniel ***@***.***> wrote: *DanielLeens* left a comment (apache/seatunnel#10708) <#10708 (comment)> Thanks, and I agree with keeping this moving. I re-checked the current repository state on dev: Debezium is still pinned at 1.9.8.Final, and this is not only an external dependency bump for SeaTunnel. We still carry copied / customized io.debezium classes in several CDC modules, so the real work here is compatibility migration. So from the current code base, the safest next step is: 1. keep this issue as the umbrella tracker 2. open a focused PR against dev 3. keep that PR scoped to Debezium 2.7.4.Final only 4. clearly list the affected connectors / copied classes in the PR description I still do not see a dev PR linked here yet, so the next concrete milestone is to get that first reviewable slice opened. A smaller connector-by-connector path will be much easier to validate than one large all-in change. — Reply to this email directly, view it on GitHub <#10708 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B74KUG6KBVTMHTFEVTJTX6D4UYAO3AVCNFSM6AAAAACXMTXP56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBUGY3TCOBZGI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>