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

DBZ-4127 Document incremental.snapshot.chunk.size

Browse Source
This commit is contained in:
Chris Cranford 2021-11-30 02:13:30 -05:00 committed by Gunnar Morling
parent 67ffc28307
commit 687b79787f
5 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2219,6 +2219,10 @@ By default, no operations are skipped.
| Fully-qualified name of the data collection that is used to send {link-prefix}:{link-signalling}[signals] to the connector.
The name format is _schema-name.table-name_.
|[[db2-property-incremental-snapshot-chunk-size]]<<db2-property-incremental-snapshot-chunk-size, `+incremental.snapshot.chunk.size+`>>
|`1024`
| The number of rows fetched from the database for each incremental snapshot iteration.
|===
[id="debezium-{context}-connector-database-history-configuration-properties"]

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

@ -2781,6 +2781,10 @@ The name format is _database-name.table-name_.
+
Note that changes to a primary key are not supported and can cause incorrect results if performed during an incremental snapshot. Another limitation is that if a schema change affects only columns' default values, then the change won't be detected until the DDL is processed from the binlog stream. This doesn't affect the snapshot events' values, but the schema of snapshot events may have outdated defaults.
|[[mysql-property-incremental-snapshot-chunk-size]]<<mysql-property-incremental-snapshot-chunk-size, `+incremental.snapshot.chunk.size+`>>
|`1024`
| The number of rows fetched from the database for each incremental snapshot iteration.
|[[mysql-property-read-only]]<<mysql-property-read-only, `+read.only+`>>
|`false`
|Switch to alternative incremental snapshot watermarks implementation to avoid writes to signal data collection

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

@ -2614,6 +2614,15 @@ You can configure the connector to skip the following types of operations:
By default, no operations are skipped.
|[[oracle-property-signal-data-collection]]<<oracle-property-signal-data-collection, `+signal.data.collection+`>>
|No default
| Fully-qualified name of the data collection that is used to send {link-prefix}:{link-signalling}[signals] to the connector.
The name format is _database_name.schema-name.table-name_.
|[[oracle-property-incremental-snapshot-chunk-size]]<<oracle-property-incremental-snapshot-chunk-size, `+incremental.snapshot.chunk.size+`>>
|`1024`
| The number of rows fetched from the database for each incremental snapshot iteration.
|===
[id="debezium-{context}-connector-database-history-configuration-properties"]

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

@ -3141,6 +3141,10 @@ By default, no operations are skipped.
|Fully-qualified name of the data collection that is used to send {link-prefix}:{link-signalling}[signals] to the connector.
The name format is _schema-name.table-name_.
|[[postgresql-property-incremental-snapshot-chunk-size]]<<postgresql-property-incremental-snapshot-chunk-size, `+incremental.snapshot.chunk.size+`>>
|`1024`
| The number of rows fetched from the database for each incremental snapshot iteration.
|===
[id="postgresql-pass-through-properties"]

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

@ -2377,6 +2377,10 @@ The name format is _database_name.schema-name.table-name_.
+
Note that changes to a primary key are not supported and can cause incorrect results if performed during an incremental snapshot. Another limitation is that if a schema change affects only columns' default values, then the change won't be detected until the DDL is processed from the binlog stream. This doesn't affect the snapshot events' values, but the schema of snapshot events may have outdated defaults.
|[[sqlserver-property-incremental-snapshot-chunk-size]]<<sqlserver-property-incremental-snapshot-chunk-size, `+incremental.snapshot.chunk.size+`>>
|`1024`
| The number of rows fetched from the database for each incremental snapshot iteration.
|[[sqlserver-property-max-iteration-transactions]]<<sqlserver-property-max-iteration-transactions, `+max.iteration.transactions+`>>
|0
|Specifies the maximum number of transactions per iteration to be used to reduce the memory footprint when streaming changes from multiple tables in a database.