DBZ-8156 Add docs for no_tables
config option for publication.autocreate.mode
This commit is contained in:
parent
fca0fdb8c4
commit
97c4ccbd52
@ -3224,11 +3224,17 @@ You grant the required permission by using the following SQL command `CREATE PUB
|
|||||||
A database administrator or the user configured to perform replications must have created the publication before running the connector.
|
A database administrator or the user configured to perform replications must have created the publication before running the connector.
|
||||||
If the connector cannot find the publication, the connector throws an exception and stops. +
|
If the connector cannot find the publication, the connector throws an exception and stops. +
|
||||||
+
|
+
|
||||||
`filtered` - If a publication exists, the connector uses it.
|
`filtered` - If a publication does not exist, the connector creates one by running a SQL command in the following format: `CREATE PUBLICATION <publication_name> FOR TABLE <tbl1, tbl2, tbl3>`. +
|
||||||
If no publication exists, the connector creates a new publication for tables that match the current filter configuration as specified by the `schema.include.list`, `schema.exclude.list`, and `table.include.list`, and `table.exclude.list` connector configuration properties.
|
|
||||||
For example: `CREATE PUBLICATION <publication_name> FOR TABLE <tbl1, tbl2, tbl3>`.
|
The resulting publication includes tables that match the current filter configuration, as specified by the `schema.include.list`, `schema.exclude.list`, `table.include.list`, and `table.exclude.list` connector configuration properties.
|
||||||
If the publication exists, the connector updates the publication for tables that match the current filter configuration.
|
|
||||||
For example: `ALTER PUBLICATION <publication_name> SET TABLE <tbl1, tbl2, tbl3>`.
|
If the publication exists, the connector updates the publication for tables that match the current filter configuration by running a SQL command in the following format: `ALTER PUBLICATION <publication_name> SET TABLE <tbl1, tbl2, tbl3>`. +
|
||||||
|
+
|
||||||
|
`no_tables` - If a publication exists, the connector uses it.
|
||||||
|
If a publication does not exist, the connector creates a publication without specifying any table by running a SQL command in the following format: `CREATE PUBLICATION <publication_name>;`.
|
||||||
|
|
||||||
|
Set the `no_tables` option if you want the connector to capture only logical decoding messages, and not capture any other change events, such as those caused by `INSERT`, `UPDATE`, and `DELETE` operations on any table.
|
||||||
|
If you select this option, to prevent the connector from emitting and processing `READ` events, you can specify names of schemas or tables for which you do not want to capture changes, for example, by using `"table.exclude.list": "public.*"` or `"schema.exclude.list": "public"`.
|
||||||
|
|
||||||
|[[postgresql-replica-autoset-type]]<<postgresql-replica-autoset-type, `+replica.identity.autoset.values+`>>
|
|[[postgresql-replica-autoset-type]]<<postgresql-replica-autoset-type, `+replica.identity.autoset.values+`>>
|
||||||
|_empty string_
|
|_empty string_
|
||||||
|
Loading…
Reference in New Issue
Block a user