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

DBZ-2918 Conscious language update: replace black-/white- list strings

Browse Source
This commit is contained in:
Bob Roldan 2021-01-21 15:30:29 -05:00 committed by Gunnar Morling
parent ecad4535b5
commit 23e8eeb854
8 changed files with 32 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/modules/ROOT/pages/connectors/cassandra.adoc
View File

@ -1004,7 +1004,7 @@ refreshing the cached Cassandra table schemas.
|`false`
|Whether deletion events should have a subsequent tombstone event (true) or not (false). It's important to note that in Cassandra, two events with the same key may be updating different columns of a given table. So this could potentially result in records being lost during compaction if they have not been consumed by the consumer yet. In other words, do NOT set this to true if you have Kafka compaction turned on.
|[[cassandra-property-field-blacklist]]
|[[cassandra-property-field-include-list]]
[[cassandra-property-field-exclude-list]]<<cassandra-property-field-exclude-list, `field.exclude.list`>>
|
|A comma-separated list of fully-qualified names of fields that should be excluded from change event message values. Fully-qualified names for fields are in the form keyspace_name>.<field_name>.<nested_field_name>.

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

@ -1764,17 +1764,17 @@ The following configuration properties are _required_ unless a default value is
|
|A list of host/port pairs that the connector uses to establish an initial connection to the Kafka cluster. This connection is used for retrieving database schema history previously stored by the connector, and for writing each DDL statement read from the source database. Each pair should point to the same Kafka cluster used by the {prodname} Kafka Connect process.
|[[db2-property-table-whitelist]]
|[[db2-property-table-include-list]]
[[db2-property-table-include-list]]<<db2-property-table-include-list, `table.include.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you want the connector to capture. Any table not included in the include list does not have its changes captured. Each identifier is of the form _schemaName_._tableName_. By default, the connector captures changes in every non-system table. Do not also set the `table.exclude.list` property.
|[[db2-property-table-blacklist]]
|[[db2-property-table-exclude-list]]
[[db2-property-table-exclude-list]]<<db2-property-table-exclude-list, `table.exclude.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you do not want the connector to capture. The connector captures changes in each non-system table that is not included in the exclude list. Each identifier is of the form _schemaName_._tableName_. Do not also set the `table.include.list` property.
|[[db2-property-column-blacklist]]
|[[db2-property-column-exclude-list]]
[[db2-property-column-exclude-list]]<<db2-property-column-exclude-list, `column.exclude.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to exclude from change event values.

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

@ -1109,25 +1109,25 @@ Only alphanumeric characters and underscores should be used.
|`false`
|When SSL is enabled this setting controls whether strict hostname checking is disabled during connection phase. If `true` the connection will not prevent man-in-the-middle attacks.
|[[mongodb-property-database-whitelist]]
|[[mongodb-property-database-include-list]]
[[mongodb-property-database-include-list]]<<mongodb-property-database-include-list, `database.include{zwsp}.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match database names to be monitored; any database name not included in `database.include.list` is excluded from monitoring. By default all databases are monitored.
Must not be used with `database.exclude.list`.
|[[mongodb-property-database-blacklist]]
|[[mongodb-property-database-exclude-list]]
[[mongodb-property-database-exclude-list]]<<mongodb-property-database-exclude-list, `database.exclude{zwsp}.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match database names to be excluded from monitoring; any database name not included in `database.exclude.list` is monitored.
Must not be used with `database.include.list`.
|[[mongodb-property-collection-whitelist]]
|[[mongodb-property-collection-include-list]]
[[mongodb-property-collection-include-list]]<<mongodb-property-collection-include-list, `collection{zwsp}.include.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match fully-qualified namespaces for MongoDB collections to be monitored; any collection not included in `collection.include.list` is excluded from monitoring. Each identifier is of the form _databaseName_._collectionName_. By default the connector will monitor all collections except those in the `local` and `admin` databases.
Must not be used with `collection.exclude.list`.
|[[mongodb-property-collection-blacklist]]
|[[mongodb-property-collection-exclude-list]]
[[mongodb-property-collection-exclude-list]]<<mongodb-property-collection-exclude-list, `collection{zwsp}.exclude.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match fully-qualified namespaces for MongoDB collections to be excluded from monitoring; any collection not included in `collection.exclude.list` is monitored. Each identifier is of the form _databaseName_._collectionName_.
@ -1141,7 +1141,7 @@ Must not be used with `collection.include.list`.
| All collections specified in `collection.include.list`
|An optional, comma-separated list of regular expressions that match names of schemas specified in `collection.include.list` for which you *want* to take the snapshot.
|[[mongodb-property-field-blacklist]]
|[[mongodb-property-field-exclude-list]]
[[mongodb-property-field-exclude-list]]<<mongodb-property-field-exclude-list, `field.exclude{zwsp}.list`>>
|_empty string_
|An optional comma-separated list of the fully-qualified names of fields that should be excluded from change event message values. Fully-qualified names for fields are of the form _databaseName_._collectionName_._fieldName_._nestedFieldName_, where _databaseName_ and _collectionName_ may contain the wildcard (*) which matches any characters.

14
documentation/modules/ROOT/pages/connectors/mysql.adoc
View File

@ -1736,7 +1736,7 @@ For details, see {link-prefix}:{link-mysql-connector}#mysql-connector-properties
"database.password": "debezium-user-pw", // <6>
"database.server.id": "184054", <7>
"database.server.name": "fullfillment", // <8>
"database.whitelist": "inventory", // <9>
"database.include.list": "inventory", // <9>
"database.history.kafka.bootstrap.servers": "kafka:9092", // <10>
"database.history.kafka.topic": "dbhistory.fullfillment", // <11>
"include.schema.changes": "true" // <12>
@ -1780,7 +1780,7 @@ For details, see {link-prefix}:{link-mysql-connector}#mysql-connector-properties
database.password: dbz
database.server.id: 184054 // <5>
database.server.name: dbserver1 // <5>
database.whitelist: inventory // <6>
database.include.list: inventory // <6>
database.history.kafka.bootstrap.servers: my-cluster-kafka-bootstrap:9092 // <7>
database.history.kafka.topic: schema-changes.inventory // <7>
----
@ -2003,31 +2003,31 @@ Only alphanumeric characters and underscores are allowed in this name.
|
|A list of host/port pairs that the connector uses for establishing an initial connection to the Kafka cluster. This connection is used for retrieving database schema history previously stored by the connector, and for writing each DDL statement read from the source database. Each pair should point to the same Kafka cluster used by the Kafka Connect process.
|[[mysql-property-database-whitelist]]
|[[mysql-property-database-include-list]]
[[mysql-property-database-include-list]]<<mysql-property-database-include-list, `database.include.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match the names of the databases for which to capture changes. The connector does not capture changes in any database whose name is not in `database.include.list`. By default, the connector captures changes in all databases.
Do not also set the `database.exclude.list` connector confiuration property.
|[[mysql-property-database-blacklist]]
|[[mysql-property-database-exclude-list]]
[[mysql-property-database-exclude-list]]<<mysql-property-database-exclude-list, `database.exclude.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match the names of databases for which you do not want to capture changes. The connector captures changes in any database whose name is not in the `database.exclude.list`.
Do not also set the `database.include.list` connector configuration property.
|[[mysql-property-table-whitelist]]
|[[mysql-property-table-include-list]]
[[mysql-property-table-include-list]]<<mysql-property-table-include-list, `table.include.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers of tables whose changes you want to capture. The connector does not capture changes in any table not included in `table.include.list`. Each identifier is of the form _databaseName_._tableName_. By default, the connector captures changes in every non-system table in each database whose changes are being captured.
Do not also specify the `table.exclude.list` connector configuration property.
|[[mysql-property-table-blacklist]]
|[[mysql-property-table-exclude-list]]
[[mysql-property-table-exclude-list]]<<mysql-property-table-exclude-list, `table.exclude.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you do not want to capture. The connector captures changes in any table not included in `table.exclude.list`. Each identifier is of the form _databaseName_._tableName_.
Do not also specify the `table.include.list` connector configuration property.
|[[mysql-property-column-blacklist]]
|[[mysql-property-column-exclude-list]]
[[mysql-property-column-exclude-list]]<<mysql-property-column-exclude-list, `column.exclude.list`>>
|_empty string_
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns to exclude from change event record values. Fully-qualified names for columns are of the form _databaseName_._tableName_._columnName_.

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

@ -1406,12 +1406,12 @@ This field is required to enable Oracle RAC support.
|_initial_
|A mode for taking an initial snapshot of the structure and optionally data of captured tables. Supported values are _initial_ (will take a snapshot of structure and data of captured tables; useful if topics should be populated with a complete representation of the data from the captured tables) and _schema_only_ (will take a snapshot of the structure of captured tables only; useful if only changes happening from now onwards should be propagated to topics). Once the snapshot is complete, the connector will continue reading change events from the database's redo logs.
|[[oracle-property-table-whitelist]]
|[[oracle-property-table-include-list]]
[[oracle-property-table-include-list]]<<oracle-property-table-include-list, `table.include.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match fully-qualified table identifiers for tables to be monitored; any table not included in the include list will be excluded from monitoring. Each identifier is of the form _schemaName_._tableName_. By default the connector will monitor every non-system table in each monitored database. May not be used with `table.exclude.list`.
|[[oracle-property-table-blacklist]]
|[[oracle-property-table-exclude-list]]
[[oracle-property-table-exclude-list]]<<oracle-property-table-exclude-list, `table.exclude.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match fully-qualified table identifiers for tables to be excluded from monitoring; any table not included in the exclude list will be monitored. Each identifier is of the form _schemaName_._tableName_. May not be used with `table.include.list`.

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

@ -2288,32 +2288,32 @@ If the publication already exists, either for all tables or configured with a su
|
|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.
|[[postgresql-property-schema-whitelist]]
|[[postgresql-property-schema-include-list]]
[[postgresql-property-schema-include-list]]<<postgresql-property-schema-include-list, `schema.include{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match names of schemas for which you *want* to capture changes. Any schema name not included in `schema.include.list` is excluded from having its changes captured. By default, all non-system schemas have their changes captured. Do not also set the `schema.exclude.list` property.
|[[postgresql-property-schema-blacklist]]
|[[postgresql-property-schema-exclude-list]]
[[postgresql-property-schema-exclude-list]]<<postgresql-property-schema-exclude-list, `schema.exclude{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match names of schemas for which you *do not* want to capture changes. Any schema whose name is not included in `schema.exclude.list` has its changes captured, with the exception of system schemas. Do not also set the `schema.include.list` property.
|[[postgresql-property-table-whitelist]]
|[[postgresql-property-table-include-list]]
[[postgresql-property-table-include-list]]<<postgresql-property-table-include-list, `table.include{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you want to capture. Any table not included in `table.include.list` does not have its changes captured. Each identifier is of the form _schemaName_._tableName_. By default, the connector captures changes in every non-system table in each schema whose changes are being captured. Do not also set the `table.exclude.list` property.
|[[postgresql-property-table-blacklist]]
|[[postgresql-property-table-exclude-list]]
[[postgresql-property-table-exclude-list]]<<postgresql-property-table-exclude-list, `table.exclude{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you *do not* want to capture. Any table not included in `table.exclude.list` has it changes captured. Each identifier is of the form _schemaName_._tableName_. Do not also set the `table.include.list` property.
|[[postgresql-property-column-whitelist]]
|[[postgresql-property-column-include-list]]
[[postgresql-property-column-include-list]]<<postgresql-property-column-include-list, `column.include{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns that should be included in change event record values. Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_. Do not also set the `column.exclude.list` property.
|[[postgresql-property-column-blacklist]]
|[[postgresql-property-column-exclude-list]]
[[postgresql-property-column-exclude-list]]<<postgresql-property-column-exclude-list, `column.exclude{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns that should be excluded from change event record values. Fully-qualified names for columns are of the form _schemaName_._tableName_._columnName_. Do not also set the `column.include.list` property.

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

@ -1867,20 +1867,20 @@ Only alphanumeric characters and underscores should be used.
|A list of host and port pairs that the connector will use for establishing an initial connection to the Kafka cluster.
This connection is used for retrieving database schema history previously stored by the connector, and for writing each DDL statement read from the source database. This should point to the same Kafka cluster used by the Kafka Connect process.
|[[sqlserver-property-table-whitelist]]
|[[sqlserver-property-table-include-list]]
[[sqlserver-property-table-include-list]]<<sqlserver-property-table-include-list, `table.include.list`>>
|
|An optional comma-separated list of regular expressions that match fully-qualified table identifiers for tables that you want {prodname} to capture; any table that is not included in `table.include.list` is excluded from capture. Each identifier is of the form _schemaName_._tableName_.
By default, the connector captures all non-system tables for the designated schemas.
Must not be used with `table.exclude.list`.
|[[sqlserver-property-table-blacklist]]
|[[sqlserver-property-table-exclude-list]]
[[sqlserver-property-table-exclude-list]]<<sqlserver-property-table-exclude-list, `table.exclude.list`>>
|
|An optional comma-separated list of regular expressions that match fully-qualified table identifiers for the tables that you want to exclude from being captured; {prodname} captures all tables that are not included in `table.exclude.list`.
Each identifier is of the form _schemaName_._tableName_. Must not be used with `table.include.list`.
|[[sqlserver-property-column-whitelist]]
|[[sqlserver-property-column-include-list]]
[[sqlserver-property-column-include-list]]<<sqlserver-property-column-include-list, `column.include.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match the fully-qualified names of columns that should be included in the change event message values.
@ -1888,7 +1888,7 @@ Fully-qualified names for columns are of the form _schemaName_._tableName_._colu
Note that primary key columns are always included in the event's key, even if not included in the value.
Do not also set the `column.exclude.list` property.
|[[sqlserver-property-column-blacklist]]
|[[sqlserver-property-column-exclude-list]]
[[sqlserver-property-column-exclude-list]]<<sqlserver-property-column-exclude-list, `column.exclude.list`>>
|_empty string_
|An optional comma-separated list of regular expressions that match the fully-qualified names of columns that should be excluded from change event message values.

8
documentation/modules/ROOT/pages/connectors/vitess.adoc
View File

@ -1089,22 +1089,22 @@ The following configuration properties are _required_ unless a default value is
|
|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.
|[[vitess-property-table-whitelist]]
|[[vitess-property-table-include-list]]
[[vitess-property-table-include-list]]<<vitess-property-table-include-list, `table.include{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you want to capture. Any table not included in `table.include.list` does not have its changes captured. Each identifier is of the form _keyspace_._tableName_. By default, the connector captures changes in every non-system table in each schema whose changes are being captured. Do not also set the `table.exclude.list` property.
|[[vitess-property-table-blacklist]]
|[[vitess-property-table-exclude-list]]
[[vitess-property-table-exclude.list]]<<vitess-property-table-exclude.list, `table.exclude{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match fully-qualified table identifiers for tables whose changes you *do not* want to capture. Any table not included in `table.exclude.list` has it changes captured. Each identifier is of the form _keyspace_._tableName_. Do not also set the `table.include.list` property.
|[[vitess-property-column-whitelist]]
|[[vitess-property-column-include-list]]
[[vitess-property-column-include-list]]<<vitess-property-column-include-list, `column.include{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns that should be included in change event record values. Fully-qualified names for columns are of the form _keyspace_._tableName_._columnName_. Do not also set the `column.exclude.list` property.
|[[vitess-property-column-blacklist]]
|[[vitess-property-column-exclude-list]]
[[vitess-property-column-exclude-list]]<<vitess-property-column-exclude-list, `column.exclude{zwsp}.list`>>
|
|An optional, comma-separated list of regular expressions that match the fully-qualified names of columns that should be excluded from change event record values. Fully-qualified names for columns are of the form _keyspace_._tableName_._columnName_. Do not also set the `column.include.list` property.