CloverDew opened a new issue, #11833: URL: https://github.com/apache/seatunnel/issues/11833
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened ### Description The MySQL CDC schema-comment E2E jobs currently pass, but their assertions do not validate the schema-change event contract introduced by the CDC comment-event support. The tests execute DDL against the source MySQL database, query the source database’s information_schema, and verify that ordinary data records continue to reach the sink. They do not verify: - which schema-change event type was emitted; - which table identifier was attached to the event; - whether the event reached the sink-side schema-change path; - whether the event was treated as a comment-only change or as a structural column modification. The current job logs show that the feature is not behaving as intended: AlterColumnCommentEvent: 0 occurrences AlterTableModifyColumnEvent columnLength=2048 sourceType=VARCHAR(512) typeChanged=true AlterTableCommentEvent tableIdentifier=.null.products changeAfter=null Not found table products This means the E2E jobs can remain green even when: - a table-comment event uses the wrong table identifier; - a comment event is dropped before reaching the sink; - a pure column-comment change is emitted as AlterTableModifyColumnEvent; - a sink receives an unsupported structural schema-change event; - the source-side catalog is not updated. The issue also exposes related integration problems: 1. The parser context can clear the MySQL database name when the null schema is set, producing identifiers such as .null.products. 2. The column-comment comparison uses non-canonical column metadata, so MySQL character-length normalization prevents comment-only classification. 3. Zeta’s deprecated schema-change dispatcher does not handle the new comment event types. 4. Databend checks the parent AlterTableColumnEvent type before checking comment events. 5. The custom MySQL parser disables Debezium parse-tree error propagation. The E2E tests should be strengthened so that they validate the actual emitted event type, table path, catalog update, and downstream handling instead of only validating source metadata and ordinary row continuity. ### SeaTunnel Version -- ### SeaTunnel Config ```conf -- ``` ### Running Command ```shell -- ``` ### Error Exception ```log -- ``` ### Zeta or Flink or Spark Version -- ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
