goutamadwant commented on issue #11037: URL: https://github.com/apache/seatunnel/issues/11037#issuecomment-4736956241
@davidzollo I went through the current MySQL CDC startup and offset path before starting. My understanding is to keep this scoped to startup.mode = specific only. I plan to add connector-owned options for gtid-set, skip-events and skip-rows, then build the startup BinlogOffset from those fields so they flow through the existing split startup offset and checkpoint/restore path. Validation would be: - specific mode requires either file+pos or gtid-set - gtid-set is mutually exclusive with file/pos for this first delivery - skip-events and skip-rows are only valid in specific mode and can be used with either base offset form - malformed GTID and negative skip values fail early I also noticed BinlogOffset already has gtids/event/row fields, but equal GTID comparison appears to check restartSkipEvents without restartSkipRows. I plan to add coverage for that and adjust it if needed. Test scope would be config validation, startup offset construction, split-state restore preservation, offset comparison, and one focused MySQL CDC runtime/IT check if it fits the existing test setup. Does this look right before I start changing the code ? -- 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]
