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
Continuing the discussion from last comments in #14991
It looks like unnest's implementation does preserve the output ordering of the columns that aren't being unnested, but it doesn't preserve their equivalence properties. This leads to situation where ordering information is lost and results in unnecessary unordered aggregation (which also breaks streaming queries that unnest and re-aggregate columns).
The text was updated successfully, but these errors were encountered:
Continuing the discussion from last comments in #14991
It looks like unnest's implementation does preserve the output ordering of the columns that aren't being unnested, but it doesn't preserve their equivalence properties. This leads to situation where ordering information is lost and results in unnecessary unordered aggregation (which also breaks streaming queries that unnest and re-aggregate columns).
The text was updated successfully, but these errors were encountered: