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

JDBC storage fails to find correct table when the same table exists in different schemas

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • 2.3.2.Final, 2.4.0.Alpha2
    • core-library
    • None
    • False
    • None
    • False

      It's not an uncommon practice when dealing with multi-tenancy that you have similar or identical table names in different schemas.

      Unfortunately, both JdbcSchemaHitsory#initializeStorage() as well as JdbcOffsetBackingStore#initializeTable() make an assumption by only passing the table name with no catalog or schema details, which can be problematic when the above scenario is at play.

      The JDBC storage module should either:

      1. Allow users to provide schema.table format for the table name.
      2. Allow passing the schema as a separate argument for the above checks.

              Unassigned Unassigned
              ccranfor@redhat.com Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: