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: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,7 @@ Types of changes:
27
27
### Fixed
28
28
29
29
- Quote table identifiers in bulk SELECTs when loading data into DuckDB memory to avoid BigQuery binder errors for identifiers that look like project IDs (e.g., `EC0601`). Added an integration test covering the quoting behavior.
30
+
- Ensure MatchRateCheck only requires the check column from the left table; the right table now only contributes join and filter columns to avoid unnecessary column selection and errors.
- The `check_column` for `MatchRateCheck` must be a column present in the left-hand table only.
6
+
- The right-hand table is only expected to provide join columns and filter columns; it must not be required to contain `check_column`.
7
+
8
+
Configuration example:
9
+
10
+
```yaml
11
+
- defaults:
12
+
check_type: MatchRateCheck
13
+
check_column: product_number # must exist on the left table
14
+
join_columns_left:
15
+
- BQ_PARTITIONTIME
16
+
- shopId
17
+
- product_number
18
+
join_columns_right:
19
+
- BQ_PARTITIONTIME
20
+
- value.shopId
21
+
- product_number
22
+
checks:
23
+
- left_table: project.dataset.left_table
24
+
right_table: project.dataset.right_table
25
+
filters:
26
+
shop_id:
27
+
value: SHOP01
28
+
```
29
+
30
+
Notes:
31
+
32
+
- The executor only requests the `check_column` from the left table during bulk loading; the right table will only be queried for its join and filter columns.
33
+
- This avoids errors when the right table does not contain the `check_column` or when its identifier resembles a BigQuery project ID.
0 commit comments