DBZ-1704 Document logical name constraints
This commit is contained in:
parent
eff3ffc345
commit
7d8f5dc7ec
@ -1371,6 +1371,7 @@ The following configuration properties are _required_ unless a default value is
|
||||
|`database.server.name`
|
||||
|
|
||||
|Logical name that identifies and provides a namespace for the particular Db2 database server being monitored. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names emanating from this connector.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`database.history.kafka.topic`
|
||||
|
|
||||
|
@ -620,6 +620,7 @@ The following configuration properties are _required_ unless a default value is
|
||||
|`mongodb.name`
|
||||
|
|
||||
|A unique name that identifies the connector and/or MongoDB replica set or sharded cluster that this connector monitors. Each server should be monitored by at most one {prodname} connector, since this server name prefixes all persisted Kafka topics emanating from the MongoDB replica set or cluster.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`mongodb.user`
|
||||
|
|
||||
|
@ -1144,6 +1144,7 @@ The following configuration properties are _required_ unless a default value is
|
||||
|`database.server.name`
|
||||
|
|
||||
|Logical name that identifies and provides a namespace for the particular Oracle database server being monitored. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names emanating from this connector.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`database.history.kafka.topic`
|
||||
|
|
||||
|
@ -1696,6 +1696,7 @@ If the publication already exists (either for all tables or configured with a su
|
||||
|`database.server.name`
|
||||
|
|
||||
|Logical name that identifies and provides a namespace for the particular PostgreSQL database server/cluster being monitored. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names coming from this connector.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`schema.whitelist`
|
||||
|
|
||||
|
@ -1358,6 +1358,7 @@ The following configuration properties are _required_ unless a default value is
|
||||
|`database.server.name`
|
||||
|
|
||||
|Logical name that identifies and provides a namespace for the particular SQL Server database server being monitored. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names emanating from this connector.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`database.history.kafka.topic`
|
||||
|
|
||||
|
@ -43,6 +43,7 @@ TIP: The {prodname} MySQL connector supports _pass-through_ configuration when c
|
||||
|`database.server.name`
|
||||
|
|
||||
|Logical name that identifies and provides a namespace for the particular MySQL database server/cluster being monitored. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names emanating from this connector.
|
||||
Only alphanumeric characters and underscores should be used.
|
||||
|
||||
|`database.server.id`
|
||||
|_random_
|
||||
|
Loading…
Reference in New Issue
Block a user