DanielLeens opened a new pull request, #11059: URL: https://github.com/apache/seatunnel/pull/11059
## Summary - add the new `Vitess-CDC` source connector module with latest and specific VGTID startup support - persist Debezium Vitess table schemas in split state so checkpoint restore can resume with stable table identity - register the connector in packaging and plugin metadata, and add English/Chinese docs and changelog entries ## Validation - `./mvnw -o spotless:apply -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-base,seatunnel-connectors-v2/connector-cdc/connector-cdc-vitess -am` - `./mvnw -o -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-base -Dtest=SourceRecordUtilsTest -DforkCount=0 test` - `./mvnw -o -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-vitess -DforkCount=0 test` - `./mvnw -o -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-vitess -Dtest=VitessSourceReaderIT -DforkCount=0 test` ## Reuse / Scope Notes - no standalone runtime script exists for SeaTunnel Vitess CDC, so validation used the module Maven test path plus the Testcontainers-based Vitess integration test - the focused Vitess integration rerun reused the locally installed `connector-cdc-base` snapshot artifact after `./mvnw -o -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-base -DskipTests install` so the latest base parsing fix was visible to the isolated Vitess module test - full reactor `-am test` was not revalidated because this worktree currently has an unrelated existing compile failure under `seatunnel-config/seatunnel-config-shade`; the Vitess/base modules touched by this change were revalidated in this run Closes #11050 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
