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

Incorrect description of whitelist and blacklist

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • 0.9.0.Alpha1
    • sqlserver-connector, website
    • None
    • Hide

      For whitelist:
      On the sqlServer create two tables.
      Configure the connector and provide database.whitelist in format "schemaName.tableName"
      Do changes in both tables.
      Check that connector have created two kafka topics (should be only one).

      For blacklist:
      On the sqlServer create two tables.
      Configure the connector and provide database.blacklist in format "schemaName.tableName"
      Do changes in both tables.
      Check that connector have created two kafka topics (should be only one).

      Show
      For whitelist: On the sqlServer create two tables. Configure the connector and provide database.whitelist in format "schemaName.tableName" Do changes in both tables. Check that connector have created two kafka topics (should be only one). For blacklist: On the sqlServer create two tables. Configure the connector and provide database.blacklist in format "schemaName.tableName" Do changes in both tables. Check that connector have created two kafka topics (should be only one).

      The blacklisting and whitelisting is not working as described by the documentation. In the documentation of the sqlserver-connector descriptions says schemaName.tableName but actually it's databaseName.schemaName.tableName (which is inline with what documentation for the code is actually saying).

      If the desired behavior is to be able to provide schemaName.tableName then it's a bug in implementation. If code is running as intended then it's a bug in the documentation. No matter what it's rather confusing.

              Unassigned Unassigned
              kleewho Łukasz Klich (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: