-
Bug
-
Resolution: Done
-
Optional
-
2.1.1.Final
-
None
Bug report
What Debezium connector do you use and what version?
1.9.7.Final (but log message is also incorrect in 2.1.x and 2.0.x).
What is the connector configuration?
Not applicable.
database.history.skip.unparseable.ddl=true
What behaviour do you expect?
The log message shouldn't contain an unfilled placeholder ("{}{}").
What behaviour do you see?
Ignoring unparseable DDL statement 'SET STATEMENT max_statement_time=60 FOR flush table': {} (io.debezium.connector.mysql.MySqlDatabaseSchema:228)
Do you see the same behaviour using the latest released Debezium version?
Yes.
Do you have the connector logs, ideally from start till finish?
Ignoring unparseable DDL statement 'SET STATEMENT max_statement_time=60 FOR flush table': {} (io.debezium.connector.mysql.MySqlDatabaseSchema:228)
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release