Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: 1.0.0.Beta1
Affects Version/s: None
Component/s: postgresql-connector, sqlserver-connector
Labels:
None

Git Pull Request:
https://github.com/debezium/debezium/pull/1063, https://github.com/debezium/debezium/pull/1077

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The tables without primary keys can contain fields with unique indices. All connectors should handle such cases in the same way

if DDL is available for the table then the primary key will be the first uniqe constraint defined either on column or as external contraint
if only JDBC metadata are available then getIndexInfo should be used to obtain information about indices - to identify if there is any unique

If no index is available then the key of the message will be null.

duplicates

DBZ-1225 Handle tables without PK consistently across all relational connectors

Closed

incorporates

DBZ-832 Add test for Oracle table without PK

Closed

DBZ-1211 Oracle connector error with tables using unique index keys: "key must not be null"

Closed

Assignee:: Jiri Pechanec

Reporter:: Jiri Pechanec

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2019/07/17 3:46 AM

Updated:: 2019/10/19 9:38 AM

Resolved:: 2019/10/19 9:38 AM