[Feature][MySQL-CDC] Add multi-database multi-table e2e testcase

[zhangshenghang]

Search before asking

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

Description

MySQL-CDC already has multi-table E2E coverage, but the current testcase only covers two tables from the same source database.

Current coverage references:

• testMysqlCdcMultiTableE2e in seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e/src/test/java/org/apache/seatunnel/connectors/seatunnel/cdc/mysql/AbstractMysqlCDCITBase.java
• /mysqlcdc_to_mysql_with_multi_table_mode_two_table.conf uses table-names = ["mysql_cdc.mysql_cdc_e2e_source_table", "mysql_cdc.mysql_cdc_e2e_source_table2"] with a single source URL jdbc:mysql://mysql_cdc_e2e:3306/mysql_cdc

The connector documentation exposes database-names and table-names, but we do not have an E2E testcase that validates one CDC job reading tables from more than one source database in multi-table mode.

It would be helpful to add a dedicated E2E testcase under seatunnel-e2e/seatunnel-connector-v2-e2e/connector-cdc-mysql-e2e to cover this scenario.

Suggested scope:

• prepare at least two source databases and multiple source tables
• run one MySQL-CDC job that captures tables from multiple databases
• verify snapshot stage and incremental insert/update/delete events
• verify sink-side table routing is correct for all captured tables
• if possible, extend restore/checkpoint coverage for the same scenario

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

[DanielLeens]

Thanks for raising this. I checked the current MySQL-CDC path and this looks like a valid E2E coverage gap.

The runtime side already accepts multiple databases through the MySQL CDC config path, but the existing E2E case only validates multiple tables under the same source database. So the missing part here is test coverage, not the value of the scenario itself.

I do not see a dev PR linked to this issue yet. If someone wants to take it, the scope looks good for a focused contribution:

1. prepare at least two source databases with multiple source tables
2. run one MySQL-CDC job covering those tables
3. verify snapshot and insert/update/delete events
4. verify sink-side routing for all captured tables

Starting from the existing testMysqlCdcMultiTableE2e test and its config would be a good approach. Keeping the first PR focused on this one scenario will make review much easier.

[nzw921rx]

@zhangshenghang I'd like to work on this issue

[julianbradford19-png]

Thank you for volunteering to work on this issue. Since zhangshenghang originally proposed the feature and expressed interest in submitting a PR, please coordinate with them to ensure there is no overlap in your efforts.

…

On Wed, Apr 8, 2026, 12:03 PM zhiwei.niu ***@***.***> wrote: *nzw921rx* left a comment (apache/seatunnel#10722) <#10722 (comment)> @zhangshenghang <https://github.com/zhangshenghang> I'd like to work on this issue — Reply to this email directly, view it on GitHub <#10722 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B74KUGZO7T4B26E3QZM4DE34U2A4LAVCNFSM6AAAAACXQN5FJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBYGAYTAOJXGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>