-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
1.5.4.Final
-
False
-
None
-
False
-
Important
When a sql with operator ->> is processed, it can not be parsed.
Bug report
2022-12-29 10:47:23,712 WARN [blc-172.19.238.10:3306] io.debezium.connector.mysql.MySqlDatabaseSchema [217] - Ignoring unparseable DDL statement '/* ApplicationName=DataGrip 2022.3 */ ALTER TABLE aaa
ADD INDEX bbb ((
CAST(ccc->>"$.ddd" as CHAR(255)) COLLATE utf8mb4_bin
)) USING BTREE': io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement '/* ApplicationName=DataGrip 2022.3 */ ALTER TABLE aaa
ADD INDEX bbb ((
CAST(ccc->>"$.ddd" as CHAR(255)) COLLATE utf8mb4_bin
)) USING BTREE'
no viable alternative at input 'ALTER TABLE aaa\n ADD INDEX bbb (('
What Debezium connector do you use and what version?
1.5.4
What is the connector configuration?
database.history.skip.unparseable.ddl = true
What is the captured database version and mode of depoyment?
mysql 8.0.21
What behaviour do you expect?
Sql is parsed normally.
What behaviour do you see?
A warning occurs.