DanielLeens commented on issue #11364: URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-4912413105
Thanks for the revision. This version is much clearer and addresses the main architecture boundaries from the first pass. From my side, the v1 direction now looks reviewable as a phased implementation: keep the shared API-facing model in `seatunnel-api`, use `connector-cdc-base` for CDC-side helpers, make the engine/API exposure additive, and start with MySQL CDC before expanding to PostgreSQL / Oracle / TiDB. Before the first implementation PR, I would only make three choices explicit so reviewers do not have to infer them from code: 1. whether v1 exposes this as an optional `cdcProgress` section in job detail or as a dedicated latest-progress endpoint 2. whether `supportLevel` is group-level in v1, with per-field support as a later refinement if needed 3. how timeout-based `STALLED` detection is configured, and how it is distinguished from connector-reported stalled states I agree with keeping UI and history/timeline storage out of v1. A narrow first PR around the model + MySQL CDC latest progress snapshot would be a good way to prove the contract without making the first delivery too large. -- 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]
