Fix incorrect SortExec removal before AggregateExec
#20245
Closed
+74
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
alamb
force-pushed
the
alamb/fix_monotonic_sort_bug
branch
from
70f8863 to
91df46f
Compare
alamb
commented
Feb 9, 2026
| } | ||
| } else if maintains_input_order.is_empty() | ||
| || !maintains_input_order.iter().any(|o| *o) | ||
| // Aggregate output columns can be computed expressions that are not |
Contributor
Author
There was a problem hiding this comment.
This is a pretty large hammer (just disables pushing grouping requirements through all AggregateExec`s convinced this is the best solution / correct yet
alamb
changed the title
SortExec removal before AggregateExec
alamb
added
optimizer
Contributor
Author
|
I am convinced we should go with option 2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Rationale for this change
Wrong answers bug was introduced in 52
What changes are included in this PR?
Fix the bug with a big hammer: simply disable the whole optimizatio
Here is an alternative PR to just disable it in a more targeted setting
SortExecremoval beforeAggregateExec(option 2) #20247Are these changes tested?
Yes, a new test is added
Are there any user-facing changes?
A bug is fixed