-
Bug
-
Resolution: Done
-
Major
-
0.8.3.Final, 0.9.0.Alpha2
-
None
My Debezium connector was running for a few weeks on a production environment. We have seven mysql shards and on Friday connectors for one of the shards has failed and went into rebalance loop. The following exception was spotted:
org.apache.kafka.connect.errors.ConnectException: no viable alternative at input 'CREATE TABLE `fibu_protocol_document`\n(\n\t`id` INTEGER NOT NULL AUTO_INCREMENT,\n\t`fibu_protocol_id` INTEGER NOT NULL,\n\t`reference_type` VARCHAR(255) NOT NULL,\n\t`reference_id` INTEGER NOT NULL,\n\t`document_number` VARCHAR(255) NOT NULL,\n\t`date` DATE NOT NULL,\n\t`contact_id` INTEGER,\n\t`contact_name` VARCHAR(160),\n\t`contact_postcode` VARCHAR(30),\n\t`contact_city` VARCHAR(50),\n\t`description` VARCHAR(80),\n\t`net_total` DECIMAL(23,6) NOT NULL,\n\t`currency_id` INTEGER NOT NULL,\n\t`created_at` DATETIME NOT NULL,\n\tPRIMARY KEY (`id`),\n\tINDEX `fibu_protocol_document_FI_1` (`fibu_protocol_id`),\n\tCONSTRAINT `fibu_protocol_document_FK_1`\n\t\tFOREIGN KEY (`fibu_protocol_id`)\n\t\tREFERENCES `fibu_protocol` (`id`),\n\tINDEX `fibu_protocol_document_FI_2` (`contact_id`),\n\tCONSTRAINT `fibu_protocol_document_FK_2`\n\t\tFOREIGN KEY (`contact_id`)\n\t\tREFERENCES `contact` (`id`),\n\tINDEX `fibu_protocol_document_FI_3` (`currency_id`),\n\tCONSTRAINT `fibu_protocol_document_FK_3`\n\t\tFOREIGN KEY (`currency_id`)\n\t\tREFERENCES `currency` (`id`)\n)ENGINE='InnoDB''
I was using antlr parser and after switching to legacy parser everything is working correctly. Originally it was working on 0.8.3.Final version, after switching to 0.9.0.Alpha2 problem still occurs.
- is related to
-
DBZ-992 Don't hard code list of supported MySQL storage engines in Antlr grammar
-
- Closed
-
