-
Bug
-
Resolution: Done
-
Major
-
3.2.1.Final
-
False
-
-
False
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
3.2.1.Final
What is the captured database version and mode of deployment?
Mariadb AWS RDS
What behavior do you expect?
DDL to be parsed
What behavior do you see?
DDL can't be parsed
Do you see the same behaviour using the latest released Debezium version?
yes
Do you have the connector logs, ideally from start till finish?
Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'ALTER TABLE IF EXISTS table MODIFY COLUMN IF EXISTS status ENUM ('PENDING', 'SENDING', 'SENT', 'SUCCESS', 'FAILED', 'FATAL') NOT NULL, RENAME COLUMN IF EXISTS col TO new_col' no viable alternative at input 'ALTER TABLE IF EXISTS table\n MODIFY COLUMN IF EXISTS status ENUM ('PENDING', 'SENDING', 'SENT', 'SUCCESS', 'FAILED', 'FATAL') NOT NULL,\n RENAME COLUMN IF EXISTS' at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43) at org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41) at org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:543) at org.antlr.v4.runtime.DefaultErrorStrategy.reportNoViableAlternative(DefaultErrorStrategy.java:310)