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

DBZ-8107 Remove references to additional-condition signal paramter

Browse Source
This commit is contained in:
roldanbob 2024-08-07 18:07:45 -04:00 committed by Jiri Pechanec
parent 3681c4365c
commit 27bb2d261b
3 changed files with 0 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
documentation/modules/ROOT/pages/configuration/signalling.adoc
View File

@ -202,14 +202,6 @@ Currently {prodname} supports the `incremental` and `blocking` types.
| An array of comma-separated regular expressions that match the fully-qualified names of the data collections to include in the snapshot. +
Specify the names by using the same format as is required for the `signal.data.collection` configuration option.
|`[.line-through]#additional-condition#`
|_N/A_
| An optional string that specifies a condition that the connector evaluates to designate a subset of records to include in a snapshot. +
+
[NOTE]
====
This property is deprecated and should be replaced by the `additional-conditions` property.
====
|`additional-conditions`
|_N/A_
@ -273,15 +265,6 @@ Currently {prodname} supports the `incremental` and `blocking` types.
| An array of comma-separated regular expressions that match the fully-qualified names of the tables to include in the snapshot. +
Specify the names by using the same format as is required for the xref:{context}-property-signal-data-collection[signal.data.collection] configuration option.
|`[.line-through]#additional-condition#`
|_N/A_
| An optional string that specifies a condition that the connector evaluates to designate a subset of records to include in a snapshot. +
[NOTE]
====
This property is deprecated and should be replaced by the `additional-conditions` property.
====
|`additional-conditions`
|_N/A_
|An optional array that specifies a set of additional conditions that the connector evaluates to determine the subset of records to include in a snapshot. +

12
documentation/modules/ROOT/partials/modules/all-connectors/con-connector-ad-hoc-snapshots.adoc
View File

@ -44,17 +44,6 @@ Currently, you can request `incremental` or `blocking` snapshots.
The format of the names is the same as for the `signal.data.collection` configuration option.
ifeval::['{context}' != 'mongodb']
|`[.line-through]#additional-condition#`
|_N/A_
| An optional string, which specifies a condition based on the column(s) of the {data-collection}(s), to capture a
subset of the contents of the {data-collection}(s). +
[NOTE]
====
This property is deprecated.
To specify criteria for defining the subset of data that you want the snapshot to capture, use the `additional-conditions` parameter.
====
|`additional-conditions`
|_N/A_
|An optional array that specifies a set of additional conditions that the connector evaluates to determine the subset of records to include in a snapshot. +
@ -66,7 +55,6 @@ You can apply different filters to each {data-collection}.
`filter`:: Specifies column values that must be present in a database record for the snapshot to include it, for example, `"color='blue'"`. +
+
The values that you assign to the `filter` parameter are the same types of values that you might specify in the `WHERE` clause of `SELECT` statements when you set the `snapshot.select.statement.overrides` property for a blocking snapshot.
In earlier {prodname} releases, an explicit `filter` parameter was not defined for snapshot signals; instead, filter criteria were implied by the values that were specified for the now deprecated `additional-condition` parameter.
endif::[]
ifeval::['{context}' != 'mongodb']

10
documentation/modules/ROOT/partials/modules/all-connectors/proc-triggering-an-incremental-snapshot-kafka.adoc
View File

@ -22,15 +22,6 @@ See the next section for more details.
| An array of comma-separated regular expressions that match the fully-qualified names of tables to include in the snapshot. +
Specify the names by using the same format as is required for the xref:{context}-property-signal-data-collection[signal.data.collection] configuration option.
|`[.line-through]#additional-condition#`
|_N/A_
| An optional string that specifies a condition that the connector evaluates to designate a subset of records to include in a snapshot. +
[NOTE]
====
This property is deprecated and should be replaced by the `additional-conditions` property.
====
|`additional-conditions`
|_N/A_
| An optional array of additional conditions that specifies criteria that the connector evaluates to designate a subset of records to include in a snapshot. +
@ -41,7 +32,6 @@ You can apply different filters to each {data-collection}.
`filter`:: Specifies column values that must be present in a database record for the snapshot to include it, for example, `"color='blue'"`. +
+
The values that you assign to the `filter` parameter are the same types of values that you might specify in the `WHERE` clause of `SELECT` statements when you set the `snapshot.select.statement.overrides` property for a blocking snapshot.
In earlier {prodname} releases, an explicit `filter` parameter was not defined for snapshot signals; instead, filter criteria were implied by the values that were specified for the now deprecated `additional-condition` parameter.
|===
An example of the execute-snapshot Kafka message: