Bug report

There are some DDL statements which can be processed by MariaDB (10.5+) but are not covered by the MySQL grammar used in Debezium.

I already fixed the same issues in the upstream project and would like to bring the fixes into the copy used in Debezium (debezium-ddl-parser) as well.

• Add variant of ALTER TABLE ADD UNIQUE IF NOT EXIST:
  • https://github.com/antlr/grammars-v4/pull/3085
• Add support for Table Value Constructors
  • https://github.com/antlr/grammars-v4/pull/3076
  • https://github.com/antlr/grammars-v4/pull/3077
• Support all privileges of MariaDB 10.6 in MySQL grammar
  • https://github.com/antlr/grammars-v4/pull/3075 

What Debezium connector do you use and what version?

Debezium Connector for MySQL 1.9.x, 2.1.3.Final, also tested with latest `main` branch of Debezium.

What is the connector configuration?

N/A

What is the captured database version and mode of deployment?

RDS for MariaDB 10.5.17

What behaviour do you expect?

The listed DDL statements should be parsed correctly using the Antlr grammar for MySQL (and MariaDB).

What behaviour do you see?

io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement [...] 

Do you see the same behaviour using the latest released Debezium version?

Tested on latest `main` branch.

Do you have the connector logs, ideally from start till finish?

N/A

How to reproduce the issue using our tutorial deployment?

N/A