-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
-
False
-
Tested with latest debezium version it is working
We've recently received ParsingException. The log says the following.
I guess it's something related to the UUID type, but it might be something else.
// code placeholder Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'CREATE TABLE `certificate_info` ( `id` BIGINT(20) AUTO_INCREMENT, `customer_id` BIGINT NOT NULL, `year` SMALLINT UNSIGNED NULL, `document_uuid` UUID NOT NULL, `generated_at` DATETIME NOT NULL, `account_id` BIGINT NOT NULL, `first_name` VARCHAR(255), `last_name` VARCHAR(255), `address` VARCHAR(255), `zipcode` VARCHAR(255), `city` VARCHAR(255), `profit` DECIMAL(18,2) NOT NULL, `profit_forward_transactions` DECIMAL(18,2) NOT NULL, `loss` DECIMAL(18,2) NOT NULL, `capital_tax` DECIMAL(18,2) NOT NULL, `solidarity_tax` DECIMAL(18,2) NOT NULL, `church_tax` DECIMAL(18,2) NOT NULL, `exemption_order` DECIMAL(18,2) NOT NULL, `church` VARCHAR(255), PRIMARY KEY (`id`), UNIQUE KEY `UK_certificate_info` (`year`, `customer_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8' no viable alternative at input 'CREATE TABLE `certificate_info` (\n `id` BIGINT(20) AUTO_INCREMENT,\n `customer_id` BIGINT NOT NULL,\n `year` SMALLINT UNSIGNED NULL,\n `document_uuid` UUID'
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
3.0.6.Final
What is the connector configuration?
<Your answer>
What is the captured database version and mode of deployment?
Mariadb AWS RDS
What behavior do you expect?
DDL should be parsed as expected