DanielLeens opened a new pull request, #11990: URL: https://github.com/apache/seatunnel/pull/11990
## Summary - synchronize this branch with the current `dev` branch and resolve the staged Debezium SPI conflicts with the upstream exact-one provider contract; - give each Zeta multi-table source configuration its own source-side child-first classloader for its dependency JAR set, and align the thread context classloader during source creation so legacy discovery resolves the same source-local dependencies; - retain the JDK 11/17 GitHub Actions baseline, including CodeQL and Docker publishing; - add regression coverage for source TCCL restoration, duplicate ServiceLoader providers, and distinct `io.debezium.*` classes loaded from separate JARs. ## Scope and Compatibility - Scope is Zeta multi-table source isolation. Each source action already carries its own connector/dependency JAR set, which the Zeta runtime uses to build the task classloader. - This change does not modify user configuration, checkpoint/savepoint serialization, or existing connector defaults. - This is not a Debezium 3 migration, a version-neutral `connector-cdc-base`, or Flink/Spark-wide multi-version support. Those need a separate, explicit compatibility effort. ## Validation - `./mvnw spotless:apply -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-base,seatunnel-engine/seatunnel-engine-core,seatunnel-engine/seatunnel-engine-client -am -nsu -Dmaven.gitcommitid.skip=true` - GitHub CI is required for compilation, unit tests, and JDK 11/17 runtime validation. ## Draft Checklist - [ ] GitHub CI is green on JDK 11 and 17 - [ ] Maintainer review confirms the Zeta-only scope and classloader lifecycle -- 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]
