Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

Debezium 3.1.3.Final

What is the connector configuration?

N/A

What is the captured database version and mode of deployment?

Amazon RDS for MariaDB 10.6

What behavior do you expect?

The following statements should be successfully parsed:

1. Rename tables

RENAME TABLES IF EXISTS TABLE11 to TABLE12, TABLE21 to TABLE22;

2. Alter table

alter table table_name CONVERT TO CHARSET utf8mb4; 

These are valid statements in MariaDB:

Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 3
Server version: 12.0.2-MariaDB-ubu2404 mariadb.org binary distributionCopyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.Type 'help;' or '\h' for help. Type '\c' to clear the current input 

MariaDB [mysql]> create table EMPLOYEE (id INT PRIMARY KEY);
Query OK, 0 rows affected (0.017 sec)

MariaDB [mysql]> rename tables if exists EMPLOYEE to EMP;
Query OK, 0 rows affected (0.008 sec)

MariaDB [mysql]> alter table EMP CONVERT TO CHARSET utf8mb4;
Query OK, 0 rows affected (0.014 sec)
Records: 0  Duplicates: 0  Warnings: 0

What behavior do you see?

[Worker-01d0d823e58f6b272] no viable alternative at input 'ALTER TABLE table_string CONVERT TO CHARSET'

Ignoring unparseable statements 'RENAME TABLES IF EXISTS third_party TO third_party_bak, company TO company_bak' stored in database schema history (io.debezium.storage.kafka.history.KafkaSchemaHistory:145)

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

Yes, issue also exists on latest main branch.