[Minor]: Produce better plan when group by contains all of the ordering requirements #7542
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #.
Rationale for this change
In the discussion @Dandandan observed that we produce unnecessary
Aggregate::Partial/Aggregate::Final
stack whereAggregate::Single
would work.This PR fixes this problem.
What changes are included in this PR?
This case arises only when ordering requirement of aggregator is among group by expressions. In these cases we now ignore ordering requirement (since each group will satisfy this requirement definitively.)
Are these changes tested?
Existing tests should work
Are there any user-facing changes?