davidzollo opened a new issue, #11037: URL: https://github.com/apache/seatunnel/issues/11037
## Background `MySQL-CDC` already exposes specific-offset startup using file/position style configuration. For GTID-enabled deployments, users often need to start from a GTID set instead of a binlog filename and position. Without GTID-based startup, failover across MySQL replicas and topology changes are harder to manage safely. ## Proposed change Add GTID-set based startup support to `MySQL-CDC` specific-offset startup. ## Expected behavior - Users can provide a GTID set as the starting position. - The connector validates incompatible combinations clearly. - Recovery semantics are documented for GTID-based startup. ## Acceptance criteria - A GTID-based startup configuration is accepted by `MySQL-CDC`. - The connector starts from the requested GTID set and continues correctly. - Validation errors are explicit when file/position and GTID configuration conflict. - English and Chinese docs are updated. - Add a focused validation path or test for GTID startup parsing and execution. ## Out of scope - Skip-events or skip-rows trimming after startup. - Snapshot-only mode. - General multi-connector offset abstraction work. -- 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]
