DanielLeens commented on issue #11049: URL: https://github.com/apache/seatunnel/issues/11049#issuecomment-4736892357
Thanks for writing this up in a much more implementation-ready way. I checked the current tree: SeaTunnel already has OceanBase JDBC source/sink support and OceanBase-specific JDBC dialect/catalog work, but we still do not have a native OceanBase CDC source under `connector-cdc`. So this reads as a valid feature request rather than a bug, and the scope here is reasonable. The main point to keep explicit before implementation is the CDC backend choice. For the first delivery, it would be better to pick one stable and testable capture path, keep it isolated inside the OceanBase connector module, and avoid broad CDC framework refactors unless they are clearly reusable. If someone takes this on, the first PR should make these parts concrete: 1. which OceanBase CDC backend is being used first, and which deployment mode it supports 2. startup semantics (`initial`, and `latest` only if recovery semantics are solid) 3. checkpoint / restore behavior 4. one runnable integration or E2E validation path, even if full CI coverage needs to be staged This is worth tracking as a feature enhancement. We've kept it under `help wanted`, and contributions are very welcome. -- 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]
