davidzollo commented on issue #7197: URL: https://github.com/apache/seatunnel/issues/7197#issuecomment-4667862120
This issue is still the right tracker for a Vitess CDC source connector, but it would help to narrow the expected delivery so a contributor can pick it up without ambiguity. ## Proposed scope Add a dedicated `connector-cdc-vitess` source connector under `seatunnel-connectors-v2/connector-cdc`. ## Functional expectations - Read change events from Vitess and map them into SeaTunnel's CDC row model. - Support table discovery/capture for the tables explicitly configured by the job. - Integrate with checkpoint/recovery so resumed jobs continue from a stable position. - Provide connector docs in both `docs/en` and `docs/zh`. - Add focused tests, including at least one runnable integration or E2E path. ## Suggested acceptance criteria - A job can start from a consistent initial position and continue to consume incremental changes. - Restart from checkpoint resumes from the correct offset/position without event loss or obvious duplication beyond the documented guarantees. - Basic multi-table capture is validated. - The connector documents required privileges, supported deployment assumptions, and current limitations. ## Out of scope for the first delivery - Sink connector work. - Broad CDC framework refactors that are not required for Vitess support. - New schema evolution policies or transform DSL work. -- 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]
