Skip to content

unnest should preserve the input's equivalence properties for uninvolved columns #15231

@vlad-arista

Description

@vlad-arista

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).

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions