DanielLeens commented on issue #11364: URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-4932227705
Thanks @goutamadwant, those v1 choices all look reasonable. To recap what I think is now ready to go: - optional `cdcProgress` section in job detail for v1 — good, this keeps the exposure additive and avoids a new endpoint in the first delivery - `supportLevel` group-level first — right call, per-field refinement can wait until the contract is proven with at least MySQL CDC - connector-reported `STALLED` vs framework timeout-based `STALLED` with explicit source/reason — this separation is important so consumers can distinguish "the connector says it's stuck" from "no progress observed within a timeout window" From my side, the STIP design boundaries are clear enough for a first implementation PR to start. A narrow first PR — shared model in `seatunnel-api`, CDC helpers in `connector-cdc-base`, MySQL CDC latest progress snapshot only — would be a good way to validate the contract without making v1 too large. The one thing I would keep visible in the PR description is how `STALLED` timeout configuration is exposed, even if the default is reasonable. That way reviewers can judge the operational ergonomics without having to infer it from the code. Looking forward to the first PR. -- 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]
