Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-5993

Log statement for unparseable DDL statement in MySqlDatabaseSchema contains placeholder

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Optional Optional
    • 2.2.0.Alpha1
    • 2.1.1.Final
    • mysql-connector
    • None
    • False
    • None
    • False
    • Low

      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.

      https://github.com/debezium/debezium/blob/edb7530866f2967f20eec0657b532caabd7e3f57/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/MySqlDatabaseSchema.java#L217

      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)

            Unassigned Unassigned
            jochen-redhat Jochen Schalanda
            Jochen Schalanda
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: