-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
2.3.2.Final, 2.4.0.Alpha2
-
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.
- duplicates
-
DBZ-6484 JDBC Schema History: When the table name is passed as dbName.tableName, the connector does not start
- Closed