SEZ9 commented on PR #11487: URL: https://github.com/apache/seatunnel/pull/11487#issuecomment-5421602290
@DanielLeens Thanks for consolidating this into a single punch list — that's exactly what I needed to close this out, and sorry for the slow reply. Direct answer: none of the four items have been pushed yet on top of `31c1e0ed`; all four are in progress and will land together in the next commit, which will be doc-only as you described. Status per item: 1. **Option-row incompatibility notes** — will add the snapshot-only restriction directly to the `stop.mode`, `startup.specific-offset.*`, and `startup.timestamp` rows in `docs/en/connectors/source/MySQL-CDC.md`, including a note on the restore-with-changed-`startup.mode` guard, rather than leaving it only in the `startup.mode` cell and the prose section. 2. **Consistency contract** — will document the semantics of `exactly_once = false` combined with snapshot-only under concurrent writes. 3. **Runtime-only failure mode** — will explicitly state that the server-id/parallelism mismatch under snapshot-only with `exactly_once` currently surfaces only as a MySQL runtime error, not config-time validation, so users aren't surprised. 4. **Smaller fixes** — will mirror the EN `exactly_once` row and FAQ updates in `docs/zh/connectors/source/MySQL-CDC.md`, correct the inaccurate "rejected by MySQL" wording, make the snapshot-only example consistent (it currently sets a server-id range without `exactly_once`), replace the literal credentials in the example with placeholders, and restore precision in the reworded FAQ answer about the binlog-resume position for initial mode. Nothing I need from you at this point. Once the commit is up I'll ping the thread so you can take the final pass you offered — appreciate you both staying with this through the long cycle. <!-- streview-comment:563 --> -- 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]
