DanielLeens commented on issue #8259: URL: https://github.com/apache/seatunnel/issues/8259#issuecomment-4402596599
Thanks for the follow-up. I rechecked the current source code, and the end-to-end capability requested in this issue is still not implemented in SeaTunnel today. The important distinction is that there are two different layers here: 1. catalog / save-mode side `TRUNCATE TABLE` support on some sinks 2. CDC source-side capture and propagation of `TRUNCATE TABLE` as a schema or data change event This issue is about the second one, and that path is still missing in the current code: - the base CDC schema change resolver only accepts `ALTER TABLE` DDL - the MySQL incremental source only advertises `ADD_COLUMN`, `DROP_COLUMN`, `RENAME_COLUMN`, and `UPDATE_COLUMN` - so even if newer Debezium versions can surface truncate events, SeaTunnel's current schema-change model still does not carry a `TRUNCATE` event through the pipeline So the previous closed state does not match the current implementation boundary. I reopened this issue so it can continue to track the missing feature properly. If someone wants to take it forward, the first minimal implementation path would likely be: 1. add a `TRUNCATE`-style change event to the SeaTunnel schema or data change model 2. let MySQL CDC recognize and emit it 3. define how downstream sinks should consume it safely 4. add docs and E2E coverage Thanks again for pointing it out. -- 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]
