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
We currently fully consume whole groups (defined as the set of rows equal under a set of ordering columns) from both the left and right input when executing EXCEPT ALL (output rows from the left side that have no matching row on the right side). I believe it's only necessary to fully consume a group from the right input and stream rows from the left.
The text was updated successfully, but these errors were encountered:
I believe so. After #21896, we'll be using the mergeJoiner and hashJoiner for set op queries, so queries without any ordering will fall back to the hash joiner, which has the behaviour @asubiotto described.
We currently fully consume whole groups (defined as the set of rows equal under a set of ordering columns) from both the left and right input when executing
EXCEPT ALL
(output rows from the left side that have no matching row on the right side). I believe it's only necessary to fully consume a group from the right input and stream rows from the left.The text was updated successfully, but these errors were encountered: