davidzollo opened a new issue, #11038: URL: https://github.com/apache/seatunnel/issues/11038
## Background In recovery and replay scenarios, starting from a known MySQL position is sometimes not enough. Users may need to skip a bounded number of events or rows after the initial offset is chosen, for example when aligning with an external cutover point. ## Proposed change Extend `MySQL-CDC` specific-offset startup with optional post-offset trimming controls for skipping a configured number of events and/or rows. ## Expected behavior - Users can keep the same base specific-offset startup mode. - Optional skip controls adjust the first consumed records after the startup offset is resolved. - The behavior is deterministic and documented. ## Acceptance criteria - `MySQL-CDC` accepts optional skip configuration together with specific-offset startup. - The first consumed records reflect the configured skip values. - Invalid combinations are rejected with clear messages. - English and Chinese docs are updated. - Add a focused test path covering skip parsing and resulting offset behavior. ## Out of scope - GTID startup support itself. - Snapshot-only startup. - Sink-side deduplication logic. -- 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]
