DBZ-1501 Document custom key mapping for Oracle
This commit is contained in:
parent
e550b2a9a0
commit
783d44ac76
@ -1770,11 +1770,11 @@ WARNING: Enabling this option may expose tables or fields explicitly blacklisted
|
||||
When `true` the delete operations are represented by a delete event and a subsequent tombstone event. When `false` only a delete event is sent. +
|
||||
Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted.
|
||||
|
||||
|`message.key.columns` 0.10.0 and later
|
||||
|`message.key.columns`
|
||||
|_empty string_
|
||||
| A semi-colon list of regular expressions that match fully-qualified tables and columns to map a primary key. +
|
||||
Each item (regular expression) must match the `<fully-qualified table>:<a comma-separated list of columns>` representing the custom key. +
|
||||
Fully-qualified tables could be defined as `DB_NAME.TABLE_NAME` or `SCHEMA_NAME.TABLE_NAME`, depending on the specific connector.
|
||||
Fully-qualified tables could be defined as `DB_NAME.TABLE_NAME` or `SCHEMA_NAME.TABLE_NAME`, depending on the specific connector.
|
||||
|
||||
|=======================
|
||||
|
||||
|
@ -1095,6 +1095,12 @@ The following configuration properties are _required_ unless a default value is
|
||||
When `true` the delete operations are represented by a delete event and a subsequent tombstone event. When `false` only a delete event is sent. +
|
||||
Emitting the tombstone event (the default behavior) allows Kafka to completely delete all events pertaining to the given key once the source record got deleted.
|
||||
|
||||
|`message.key.columns`
|
||||
|_empty string_
|
||||
| A semi-colon list of regular expressions that match fully-qualified tables and columns to map a primary key. +
|
||||
Each item (regular expression) must match the `<fully-qualified table>:<a comma-separated list of columns>` representing the custom key. +
|
||||
Fully-qualified tables could be defined as `DB_NAME.TABLE_NAME` or `SCHEMA_NAME.TABLE_NAME`, depending on the specific connector.
|
||||
|
||||
|`column.propagate.source.type`
|
||||
|_n/a_
|
||||
|An optional comma-separated list of regular expressions that match the fully-qualified names of columns whose original type and length should be added as a parameter to the corresponding field schemas in the emitted change messages.
|
||||
|
@ -1567,7 +1567,7 @@ The schema parameters `pass:[_]pass:[_]debezium.source.column.type`, `pass:[_]pa
|
||||
Useful to properly size corresponding columns in sink databases.
|
||||
Fully-qualified names for columns are of the form _databaseName_._tableName_._columnName_, or _databaseName_._schemaName_._tableName_._columnName_.
|
||||
|
||||
|`message.key.columns` 0.10.0 and later
|
||||
|`message.key.columns`
|
||||
|_empty string_
|
||||
| A semi-colon list of regular expressions that match fully-qualified tables and columns to map a primary key. +
|
||||
Each item (regular expression) must match the fully-qualified `<fully-qualified table>:<a comma-separated list of columns>` representing the custom key. +
|
||||
|
@ -1253,7 +1253,7 @@ Useful to properly size corresponding columns in sink databases.
|
||||
Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_.
|
||||
|
||||
|
||||
|`message.key.columns` 0.10.0 and later
|
||||
|`message.key.columns`
|
||||
|_empty string_
|
||||
| A semi-colon list of regular expressions that match fully-qualified tables and columns to map a primary key. +
|
||||
Each item (regular expression) must match the fully-qualified `<fully-qualified table>:<a comma-separated list of columns>` representing the custom key. +
|
||||
|
Loading…
Reference in New Issue
Block a user