-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
1.7.2.Final
-
None
-
False
-
None
-
False
-
Low
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
1.7.2.Final
debezium-connector-mysql
What is the connector configuration?
{ "name": "XXX", "snapshot.mode": "when_needed", "connector.class": "io.debezium.connector.mysql.MySqlConnector", "tasks.max": "1", "database.hostname": "localhost", "database.port": "3306", "database.user": "XXX", "database.password": "XXX", "database.server.id": "3342", "database.server.name": "XXX", "database.include.list": "XXX", "database.history.kafka.bootstrap.servers": "localhost:9092", "database.history.kafka.topic": "XXX.sys.history.0", "internal.database.history.ddl.filter": "# D.*", "event.processing.failure.handling.mode": "warn", "database.history.skip.unparseable.ddl": "true", "table.include.list":"XXXX", "include.schema.changes": false, "errors.log.enable": true, "errors.log.include.messages": true, "key.converter": "org.apache.kafka.connect.storage.StringConverter", "key.converter.schemas.enable": false, "value.converter": "org.apache.kafka.connect.json.JsonConverter", "value.converter.schemas.enable": false, "topic.creation.default.replication.factor": 1, "topic.creation.default.partitions": 1, "topic.creation.default.cleanup.policy": "compact", "tombstones.on.delete": false, "transforms": "unwrap,reroute", "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState", "transforms.unwrap.drop.tombstones": true, "transforms.unwrap.delete.handling.mode": "drop", "transforms.unwrap.add.fields": "op,table,ts_ms:processed_at,source.ts_ms:emitted_at", "transforms.unwrap.add.headers": "db", "transforms.reroute.type": "io.debezium.transforms.ByLogicalTableRouter", "transforms.reroute.key.enforce.uniqueness": false, "transforms.reroute.topic.regex": "(.*)" , "transforms.reroute.topic.replacement": "$1.0" }
What is the captured database version and mode of deployment?
(E.g. on-premises, with a specific cloud provider, etc.)
on-premises, mariaDB 10.4.6
What behaviour do you expect?
no warnings
What behaviour do you see?
[2022-12-09 13:36:03,822] WARN [XXX.0|task-0] Ignoring unparseable statements 'CREATE INDEX IF NOT EXISTS i_table_prvt_col ON some_table(is_private_column)' stored in database history: {} io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'CREATE INDEX IF NOT EXISTS i_table_prvt_col ON some_table(is_private_column)' no viable alternative at input 'CREATE INDEX IF' at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43) at org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41) at org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:544) at org.antlr.v4.runtime.DefaultErrorStrategy.reportNoViableAlternative(DefaultErrorStrategy.java:310) at org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:136) at io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:1194) at io.debezium.ddl.parser.mysql.generated.MySqlParser.root(MySqlParser.java:922) at io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:72) at io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:45) at io.debezium.antlr.AntlrDdlParser.parse(AntlrDdlParser.java:82) at io.debezium.relational.history.AbstractDatabaseHistory.lambda$recover$1(AbstractDatabaseHistory.java:136) at io.debezium.relational.history.KafkaDatabaseHistory.recoverRecords(KafkaDatabaseHistory.java:311) at io.debezium.relational.history.AbstractDatabaseHistory.recover(AbstractDatabaseHistory.java:103) at io.debezium.relational.HistorizedRelationalDatabaseSchema.recover(HistorizedRelationalDatabaseSchema.java:50) at io.debezium.connector.mysql.MySqlConnectorTask.validateAndLoadDatabaseHistory(MySqlConnectorTask.java:333) at io.debezium.connector.mysql.MySqlConnectorTask.start(MySqlConnectorTask.java:106) at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:133) at org.apache.kafka.connect.runtime.WorkerSourceTask.initializeAndStart(WorkerSourceTask.java:231) at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:186) at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:237) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: org.antlr.v4.runtime.NoViableAltException at org.antlr.v4.runtime.atn.ParserATNSimulator.noViableAlt(ParserATNSimulator.java:2026) at org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:467) at org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:393) at io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:996) ... 19 more
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Not yet tested
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
Yes
- is incorporated by
-
DBZ-4841 Debezium Mysql connector can't handle CREATE INDEX IF NOT EXISTS (MariaDB)
- Closed