alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-1704 Document logical name constraints

Browse Source
This commit is contained in:
Jiri Pechanec 2020-02-14 13:45:04 +01:00 committed by Gunnar Morling
parent eff3ffc345
commit 7d8f5dc7ec
6 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
documentation/modules/ROOT/pages/connectors/db2.adoc
View File

@ -1371,6 +1371,7 @@ The following configuration properties are _required_ unless a default value is
|`database.server.name` |`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. |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` |`database.history.kafka.topic`
| |

1
documentation/modules/ROOT/pages/connectors/mongodb.adoc
View File

@ -620,6 +620,7 @@ The following configuration properties are _required_ unless a default value is
|`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. |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` |`mongodb.user`
| |

1
documentation/modules/ROOT/pages/connectors/oracle.adoc
View File

@ -1144,6 +1144,7 @@ The following configuration properties are _required_ unless a default value is
|`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. |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` |`database.history.kafka.topic`
| |

1
documentation/modules/ROOT/pages/connectors/postgresql.adoc
View File

@ -1696,6 +1696,7 @@ If the publication already exists (either for all tables or configured with a su
|`database.server.name` |`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. |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` |`schema.whitelist`
| |

1
documentation/modules/ROOT/pages/connectors/sqlserver.adoc
View File

@ -1358,6 +1358,7 @@ The following configuration properties are _required_ unless a default value is
|`database.server.name` |`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. |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` |`database.history.kafka.topic`
| |

1
documentation/modules/ROOT/pages/modules/cdc-mysql-connector/r_mysql-connector-configuration-properties.adoc
View File

@ -43,6 +43,7 @@ TIP: The {prodname} MySQL connector supports _pass-through_ configuration when c
|`database.server.name` |`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. |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` |`database.server.id`
|_random_ |_random_