fatmanverse opened a new pull request, #11487: URL: https://github.com/apache/seatunnel/pull/11487
### Purpose of this pull request Closes #11036. This pull request adds a dedicated `startup.mode = "snapshot"` option for bounded MySQL CDC bootstrap jobs. It reuses the existing snapshot split planning and reading path, reports the source as bounded, and finishes without creating an incremental/binlog split. The snapshot-only completion path depends only on snapshot split completion, so parallel batch jobs can finish without requiring a checkpoint. Incompatible combinations with non-`never` stop modes, `exactly_once`, and binlog-specific startup offsets fail fast. ### Does this PR introduce _any_ user-facing change? Yes. Previously, MySQL CDC could either read a snapshot and continue into binlog streaming, or start from a binlog-oriented position. There was no first-class bounded snapshot-only mode. Users can now configure: ```hocon startup.mode = "snapshot" ``` The source reads the configured snapshot and exits successfully without consuming subsequent binlog events. Existing startup modes and other CDC connectors keep their current behavior. ### How was this patch tested? - `./mvnw spotless:apply` - `./mvnw -pl seatunnel-connectors-v2/connector-cdc/connector-cdc-base -DskipIT test` - 61 tests passed - `./mvnw -q -DskipTests verify` - `MysqlCDCSnapshotOnlyIT` - 5 container invocations passed with parallelism 2 and checkpointing disabled - `git diff --check` ### Check list * [x] No new JAR binary package is added. * [x] English and Chinese connector documentation is updated. * [x] No incompatible configuration or API change is introduced. * [x] A focused MySQL CDC E2E test is added. * [x] Plugin mapping, distribution dependencies, labels, and plugin configuration do not require changes for this existing connector. -- 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]
