DBZ-3427 Change wording in connector field database.server.name

This commit is contained in:
Anisha Mohanty 2021-04-28 15:23:57 +05:30 committed by Gunnar Morling
parent a6b54c7000
commit 98ce954332
7 changed files with 7 additions and 7 deletions

View File

@ -1878,7 +1878,7 @@ The following configuration properties are _required_ unless a default value is
|[[db2-property-database-server-name]]<<db2-property-database-server-name, `+database.server.name+`>>
|
|Logical name that identifies and provides a namespace for the particular Db2 database server that hosts the database for which {prodname} is capturing changes. Only alphanumeric characters and underscores should be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|Logical name that identifies and provides a namespace for the particular Db2 database server that hosts the database for which {prodname} is capturing changes. Only alphanumeric characters and underscores must be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|[[db2-property-database-history-kafka-topic]]<<db2-property-database-history-kafka-topic, `+database.history.kafka.topic+`>>
|

View File

@ -1101,7 +1101,7 @@ The following configuration properties are _required_ unless a default value is
|[[mongodb-property-mongodb-name]]<<mongodb-property-mongodb-name, `+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.
Only alphanumeric characters and underscores must be used.
|[[mongodb-property-mongodb-user]]<<mongodb-property-mongodb-user, `+mongodb.user+`>>
|

View File

@ -2150,7 +2150,7 @@ The following configuration properties are _required_ unless a default value is
|[[mysql-property-database-server-name]]<<mysql-property-database-server-name, `+database.server.name+`>>
|
|Logical name that identifies and provides a namespace for the particular MySQL database server/cluster in which {prodname} is capturing changes. The logical name should be unique across all other connectors, since it is used as a prefix for all Kafka topic names that receive events emitted by this connector.
Only alphanumeric characters and underscores are allowed in this name.
Only alphanumeric characters and underscores must be used in the database server logical name.
|[[mysql-property-database-server-id]]<<mysql-property-database-server-id, `+database.server.id+`>>
|_random_

View File

@ -1261,7 +1261,7 @@ The following configuration properties are _required_ unless a default value is
|[[oracle-property-database-server-name]]<<oracle-property-database-server-name, `+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.
Only alphanumeric characters and underscores must be used.
|[[oracle-property-database-connection-adapter]]<<oracle-property-database-connection-adapter, `+database.connection.adapter+`>>
|`logminer`

View File

@ -2503,7 +2503,7 @@ If the publication already exists, either for all tables or configured with a su
|[[postgresql-property-database-server-name]]<<postgresql-property-database-server-name, `+database.server.name+`>>
|
|Logical name that identifies and provides a namespace for the particular PostgreSQL database server or cluster in which {prodname} is capturing changes. Only alphanumeric characters and underscores should be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|Logical name that identifies and provides a namespace for the particular PostgreSQL database server or cluster in which {prodname} is capturing changes. Only alphanumeric characters and underscores must be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|[[postgresql-property-schema-include-list]]<<postgresql-property-schema-include-list, `+schema.include.list+`>>
|

View File

@ -1993,7 +1993,7 @@ The following configuration properties are _required_ unless a default value is
|[[sqlserver-property-database-server-name]]<<sqlserver-property-database-server-name, `+database.server.name+`>>
|
|Logical name that identifies and provides a namespace for the SQL Server database server that you want {prodname} to capture. 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.
Only alphanumeric characters and underscores must be used.
|[[sqlserver-property-database-history-kafka-topic]]<<sqlserver-property-database-history-kafka-topic, `+database.history.kafka.topic+`>>
|

View File

@ -1090,7 +1090,7 @@ The following configuration properties are _required_ unless a default value is
|[[vitess-property-database-server-name]]<<vitess-property-database-server-name, `+database.server.name+`>>
|
|Logical name that identifies and provides a namespace for the particular Vitess database server or cluster in which {prodname} is capturing changes. Only alphanumeric characters and underscores should be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|Logical name that identifies and provides a namespace for the particular Vitess database server or cluster in which {prodname} is capturing changes. Only alphanumeric characters and underscores must be used in the database server logical name. The logical name should be unique across all other connectors, since it is used as a topic name prefix for all Kafka topics that receive records from this connector.
|[[vitess-property-table-include-list]]<<vitess-property-table-include-list, `+table.include.list+`>>
|