davidzollo commented on issue #11364:
URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-4945081157
Thanks for opening this. I agree this should not be duplicated.
To make the proposal easier to evaluate and implement incrementally, I
suggest making the validation path and acceptance boundary more explicit.
## Suggested validation path
1. Validate a multi-table MySQL CDC job and confirm the model can clearly
distinguish `SNAPSHOT`, `CATCH_UP`, `INCREMENTAL`, and `RESTORING`.
2. Validate a restore scenario and confirm users can compare:
- last checkpointed position
- restored position
- first observed post-restore progress
3. Validate a stalled or delayed scenario and confirm the output makes it
clear whether the signal came from:
- connector-reported evidence, or
- framework timeout / no-progress observation
4. Validate partial-support connectors and confirm unsupported fields are
returned as unsupported or unavailable rather than misleading defaults.
## Suggested acceptance criteria for v1
- The latest CDC progress snapshot is available through an additive API path.
- Users can distinguish snapshot, incremental, and restore-related progress
without reading connector-specific logs.
- The model preserves connector-native raw position details where needed.
- Unsupported progress fields are explicitly marked instead of guessed.
- At least one primary connector family and one follow-up connector family
complete the first implementation path successfully.
- The docs clearly explain the difference between normalized fields and
connector-native raw fields.
## Suggested implementation discipline
I would also recommend keeping v1 intentionally narrow:
- latest snapshot only
- no long-term history store yet
- no UI-first dependency
- no promise that every connector exposes identical lag semantics
That boundary should make the first implementation much easier to land
without overcommitting the long-term contract.
--
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]
