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
The table is partitioned by x, so when merging in new data where x=1, I would expect only one partition to be touched.
The output from the merge operation is {'num_source_rows': 1, 'num_target_rows_inserted': 0, 'num_target_rows_updated': 1, 'num_target_rows_deleted': 0, 'num_target_rows_copied': 2, 'num_output_rows': 3, 'num_target_files_added': 3, 'num_target_files_removed': 3, ...}
which indicates that all three partitions are processed.
So my questions are:
Is there any way doing a merge that only touches certain partitions?
If not: Are there any plans for implementing such a feature?
The text was updated successfully, but these errors were encountered:
Description
From what I can see, the merge operation touches all partitions, instead of only touching those that are relevant for the data to be merged.
Example:
The table is partitioned by
x
, so when merging in new data wherex=1
, I would expect only one partition to be touched.The output from the merge operation is
{'num_source_rows': 1, 'num_target_rows_inserted': 0, 'num_target_rows_updated': 1, 'num_target_rows_deleted': 0, 'num_target_rows_copied': 2, 'num_output_rows': 3, 'num_target_files_added': 3, 'num_target_files_removed': 3, ...}
which indicates that all three partitions are processed.
So my questions are:
The text was updated successfully, but these errors were encountered: