-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
1.5.0.Final
-
None
-
False
-
False
-
Undefined
-
ECS instances were rotated which resulted in debezium kafka connect container getting restarted. After container restart, it started giving
io.debezium.text.ParsingException: DDL statement couldn't be parsed
But this DDL command was fired 25 days ago("ts_sec" : 1625928471).
2021-08-04 05:57:02,269 ERROR || Unexpected exception while processing record 'ConsumerRecord(topic = schema-history.db, partition = 0, leaderEpoch = 1, offset = 96, CreateTime = 1625928471859, serialized key size = -1, serialized value size = 334, headers = RecordHeaders(headers = [], isReadOnly = false), key = null, value = { "source" : { "server" : "db_json" }, "position" : { "transaction_id" : null, "ts_sec" : 1625928471, "file" : "mysql-bin-changelog.000070", "pos" : 93488166, "server_id" : XXXXXXX }, "databaseName" : "db", "ddl" : "`table_name` to `table_name_bkp`", "tableChanges" : [ ] })' [io.debezium.relational.history.KafkaDatabaseHistory] io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement '`table_name` to `table_name_bkp`' mismatched input '`table_name`' expecting {<EOF>, 'ALTER', 'ANALYZE', 'CALL', 'CHANGE', 'CHECK', 'CREATE', 'DELETE', 'DESC', 'DESCRIBE', 'DROP', 'EXPLAIN', 'GET', 'GRANT', 'INSERT', 'KILL', 'LOAD', 'LOCK', 'OPTIMIZE', 'PURGE', 'RELEASE', 'RENAME', 'REPLACE', 'RESIGNAL', 'REVOKE', 'SELECT', 'SET', 'SHOW', 'SIGNAL', 'UNLOCK', 'UPDATE', 'USE', 'BEGIN', 'BINLOG', 'CACHE', 'CHECKSUM', 'COMMIT', 'DEALLOCATE', 'DO', 'FLUSH', 'HANDLER', 'HELP', 'INSTALL', 'PREPARE', 'REPAIR', 'RESET', 'ROLLBACK', 'SAVEPOINT', 'START', 'STOP', 'TRUNCATE', 'UNINSTALL', 'XA', 'EXECUTE', 'SHUTDOWN', '--', '(', ';'}
Why is the DDL malformed? This DDL is not a valid SQL command
- duplicates
-
DBZ-3399 Rename table stores only a fragment of DDL in schema history
- Closed