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

Debezium does not include column made by Unique Key using HASH in schema in MariaDB

XMLWordPrintable

    • False
    • None
    • False
    • Moderate

      Debezium MySQL connector 2.6.1.Final to read a MySQL database table, but currently Debezium cannot read the binlog as it encounters an error that internal schema size does not match row size. The table being read is generating a column made by a HASH which is not in the original schema but is included in event updates in the binlog, which leads to the mismatch in row and schema size.

      For context, this revolves around MariaDB "USING HASH" for unique keys. This adds a hidden column called "DB_HASH_ROW_1" to the table that debezium does not see, and will cause an error when checking the binlog due to the added row not present in the schema. This Hash is only used when the Unique Key in MariaDB exceeds the maximum length for a BTREE in the unique key.

      The discussion leading to this issue:
      https://groups.google.com/g/debezium/c/MYq3pBAUM0k/m/9J4T5t52AQAJ?utm_medium=email&utm_source=footer&pli=1

            Unassigned Unassigned
            konrad.sokun Konrad Sokun (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: