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

Dummy event replacing event type 160 that slave cannot handle

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.1.1.Final
    • Fix Version/s: None
    • Component/s: mysql-connector
    • Labels:
      None

      Description

      Hi all, 

      I have setup Debezium for MariaDB version 10.2.14. I used schema_only for  snapshot.mode in the connector. everything works well, but when I consume data from history topic, I can see lots of these messages:

      {
           "source" :

      {      "server" : "test_mysql"      }

      ,
      "position" :

      {     "ts_sec" : 1593226436,     "file" : "mariadb-bin.084342",     "pos" : 15776524,     "server_id" : 25,     "event" : 1 }

      ,
          "databaseName" : "",
           "ddl" : "# Dummy event replacing event type 160 that slave cannot handle. "
      }

      As far as I know, event type 160 is for ANNOTATE_ROWS_EVENT (events accompany row events and describe the query which caused the row event).

      why we have these events for schema_only mode? (this type of event is related to row event)

      what should I do?

      This is producing a huge of dummy data in the history topic and I can not restart the connector. I have to delete the history topic and use schema_only_recovery each time.

      Thank you. 

       

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  aminkr amin kavosi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: