DanielLeens commented on issue #8259: URL: https://github.com/apache/seatunnel/issues/8259#issuecomment-4436398900
I rechecked the current `dev` code after the manual close, and I do not see a merged implementation that makes this feature available end to end yet. Reopening this issue is the safer way to keep the tracker aligned with the actual capability boundary. The current source boundary is still the same: - the base CDC schema-change resolver only accepts `ALTER TABLE`-style DDL; - the MySQL incremental source still advertises only `ADD_COLUMN`, `DROP_COLUMN`, `RENAME_COLUMN`, and `UPDATE_COLUMN` support; - sink-side catalog `TRUNCATE TABLE` support is a different capability from CDC source-side capture and downstream propagation. So even if some lower-level dependency can surface truncate-related events, SeaTunnel itself still does not carry a `TRUNCATE`-style change through the current CDC event model and sink-consumption path. Because of that, this issue should stay open until there is an actual merged implementation for the feature requested here. The first minimal implementation path still looks like: 1. add a `TRUNCATE`-style event to the SeaTunnel CDC/schema-change model; 2. let MySQL CDC recognize and emit it; 3. define how downstream sinks consume it safely; 4. add docs and E2E coverage. Thanks again for calling out the gap earlier. -- 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]
