DanielLeens commented on issue #11364: URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-4953553901
Thanks for sending the DISCUSS thread to dev@ and for tightening the issue body with the flowchart, validation path, and acceptance criteria. I also noticed PR #11395 is now open. The current sequencing looks sensible: start with the shared progress model in `seatunnel-api`, keep the CDC helper path narrow, and validate the contract with MySQL CDC first instead of mixing every downstream exposure into the same first change. That first slice is useful because it lets reviewers focus on whether the contract itself is sound. If #11395 lands cleanly, follow-up work like exposing optional `cdcProgress` in job detail, expanding connector coverage, and refining `STALLED` / restore visibility can iterate on top of a smaller and easier-to-review foundation. -- 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]
