goutamadwant opened a new pull request, #13239: URL: https://github.com/apache/seatunnel/pull/13239
### Purpose of this pull request First slice of STIP-30 (#11364), split out of #11512 as requested there: the API only. Adds `org.apache.seatunnel.api.cdc` and the `SupportCdcProgress` marker so a CDC source can hand the engine an immutable snapshot of its latest progress. All types are `@Experimental`. - Reader and enumerator reports stay separate; neither infers the other's state. - Every value carries its own accuracy (`EXACT`, `BEST_EFFORT`, `UNSUPPORTED`, `UNAVAILABLE`). Nothing is guessed or defaulted to zero. - Positions keep the connector's native coordinates under an explicit position family. - `CdcProgressLifecycle` is derived from the split, so it means the same thing in every startup mode; `COMPLETED` covers bounded jobs. `docs/en/developer/cdc-progress.md` states the provider guarantees and the expected lifecycle, assignment status and position accuracy for each startup mode (`initial`, `snapshot-only`, `earliest`, `latest`, `specific`, `timestamp`, `committed-offset`). Not in this slice: connector implementations and engine collection. Those follow as separate PRs on top of this one; the current `connector-cdc-base` and Zeta code is in #11512. Checkpoint and restore positions are left out until the restore lifecycle is wired. ### Does this PR introduce _any_ user-facing change? No runtime change. New experimental API and a developer doc. ### How was this patch tested? `CdcProgressModelTest`: immutability and defensive copies, count validation, accuracy payload rules, reader report null and optional-field handling. `seatunnel-api` passes on JDK 11 and 17 (422 tests). ### Check list * [x] If necessary, please update the documentation to describe the new feature. -- 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]
