-
Bug
-
Resolution: Done
-
Major
-
0.10.0.CR1
-
None
Upon working with Debezium 0.9.5 (checked for Debezium 10.0.0.Beta2 too) I've encountered a problem while reading the binlog. I've changed the table name to <table>.
"tasks":[{"id":0,"state":"FAILED","worker_id":"10.8.147.153:8083","trace":"org.apache.kafka.connect.errors.ConnectException: no viable alternative at input 'GRANT DELETE ON <table>'\n\tat io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230)\n\tat io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:208)\n\tat io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:517)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.notifyEventListeners(BinaryLogClient.java:1095)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.listenForEventPackets(BinaryLogClient.java:943)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient.connect(BinaryLogClient.java:580)\n\tat com.github.shyiko.mysql.binlog.BinaryLogClient$7.run(BinaryLogClient.java:825)\n\tat java.lang.Thread.run(Thread.java:748)\nCaused by: io.debezium.text.ParsingException: no viable alternative at input 'GRANT DELETE ON <table>'\n\tat io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:40)\n\tat org.antlr.v4.runtime.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41)\n\tat org.antlr.v4.runtime.Parser.notifyErrorListeners(Parser.java:544)\n\tat org.antlr.v4.runtime.DefaultErrorStrategy.reportNoViableAlternative(DefaultErrorStrategy.java:282)\n\tat org.antlr.v4.runtime.DefaultErrorStrategy.reportError(DefaultErrorStrategy.java:121)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:1078)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.root(MySqlParser.java:812)\n\tat io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:68)\n\tat io.debezium.connector.mysql.antlr.MySqlAntlrDdlParser.parseTree(MySqlAntlrDdlParser.java:41)\n\tat io.debezium.antlr.AntlrDdlParser.parse(AntlrDdlParser.java:80)\n\tat io.debezium.connector.mysql.MySqlSchema.applyDdl(MySqlSchema.java:305)\n\tat io.debezium.connector.mysql.BinlogReader.handleQueryEvent(BinlogReader.java:709)\n\tat io.debezium.connector.mysql.BinlogReader.handleEvent(BinlogReader.java:501)\n\t... 5 more\nCaused by: org.antlr.v4.runtime.NoViableAltException\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.noViableAlt(ParserATNSimulator.java:2023)\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.execATN(ParserATNSimulator.java:467)\n\tat org.antlr.v4.runtime.atn.ParserATNSimulator.adaptivePredict(ParserATNSimulator.java:393)\n\tat io.debezium.ddl.parser.mysql.generated.MySqlParser.sqlStatements(MySqlParser.java:886)\n\t... 12 more
- is duplicated by
-
-
- Closed
-
[DBZ-1411] Debezium for MySQL fails on GRANT DELETE ON <table>
yaniv ranen (Inactive)
added a comment - jpechane the exact DDL was -
GRANT DELETE ON starterview.rule_link TO 'svc_alerts'@'%'
yaniv ranen (Inactive)
added a comment - jpechane the exact DDL was -
GRANT DELETE ON starterview.rule_link TO 'svc_alerts'@'%' 
Jiri Pechanec
added a comment - Yes, this looks like the issue. No I really need the exact DDL how is in logs - esp. if there are any apostrophes around the database/table name
Jiri Pechanec
added a comment - Yes, this looks like the issue. No I really need the exact DDL how is in logs - esp. if there are any apostrophes around the database/table name yaniv ranen (Inactive)
added a comment - ok, the table name is - starterview.rule_link Jiri Pechanec
added a comment - Hi, thanks for the report, I am afraid that the table name might be important, see e.g. DBZ-1300
Jiri Pechanec
added a comment - Hi, thanks for the report, I am afraid that the table name might be important, see e.g. DBZ-1300 
Released