You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/docs/connectors/pipeline-connectors/mysql.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -368,11 +368,10 @@ pipeline:
368
368
<td>scan.snapshot.filters</td>
369
369
<td>optional</td>
370
370
<td style="word-wrap: break-word;">(none)</td>
371
-
<td>String</td>
372
-
<td>When reading a table snapshot, the rows of captured tables will be filtered using the specified filter expression (AKA a SQL WHERE clause). <br>
373
-
By default, no filter is applied, meaning the entire table will be synchronized. <br>
374
-
A colon (:) separates table name and filter expression, while a semicolon (;) separate multiple filters,
375
-
e.g. `db1.user_table_[0-9]+:id > 100;db[1-2].[app|web]_order_\\.*:id < 0;`.
371
+
<td>List<Map<String, String>></td>
372
+
<td>When reading a table snapshot, the rows of captured tables will be filtered using the specified filter expressions (SQL WHERE clauses). <br>
373
+
This option is configured as a list of filter specifications, where each specification is represented as a map of string key-value pairs (as shown in the example configuration below). <br>
374
+
By default, no filter is applied, meaning the entire table will be synchronized.
0 commit comments