io.debezium.text.ParsingException: DDL statement couldn't be parsed

Root cause

Debezium's DDL parser encountered a SQL statement it does not support — typically a MySQL/MariaDB extension, a reserved word used as a column name, or a feature introduced in a DB version newer than Debezium's parser.

How to fix

1. Short-term workaround: set schema.history.internal.skip.unparseable.ddl=true to skip unparseable DDL (may cause schema drift; use with caution).
2. Identify the problematic DDL from the stack trace and check if it uses reserved keywords as identifiers (wrap with backticks).
3. Upgrade Debezium to the latest version — DDL parser improvements are released regularly.
4. Report the failing DDL statement as a bug at github.com/debezium/debezium/issues.