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

Ignore non-existing table reported on Aurora via SHOW TABLES

    Details

    • Steps to Reproduce:
      Hide

      AWS Aurora for MySQL (latest) has a bug in which `mysql.host` is reported as existing from `SHOW TABLES` but actually doesn't exist at all making the schema capture of this table fails in Debezium and preventing the connector to start up.

      Show
      AWS Aurora for MySQL (latest) has a bug in which `mysql.host` is reported as existing from `SHOW TABLES` but actually doesn't exist at all making the schema capture of this table fails in Debezium and preventing the connector to start up.

      Description

      When `table.ignore.builtin` is set to True, one might expect the tables under the `mysql` schema to be completely ignored from both (data) capture and schema capture.

      Nevertheless those tables get registered in the `createTablesMap` map because the condition `createTableFilters == filters && shouldRecordTableSchema` is True whenever is `isStoreOnlyMonitoredTablesDdl` set since `!schema.isStoreOnlyMonitoredTablesDdl()` will be true by default and therefore shouldRecordTableSchema(schema, filters, id) will return true, even for builtin table.

      It's not really clear if these is any added value of capturing builtin tables schema, if not, probably this behaviour needs to be changed to fully and completely ignore built-in tables.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ebrard Emmanuel Brard
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: