Fix AVG groups accummulator ignoring return type #10114
Merged
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
physical-expr
gruuya
commented
Apr 17, 2024
| 12)--------------PlaceholderRowExec | ||
|
|
||
| query IIII | ||
| query IIII rowsort |
There was a problem hiding this comment.
I found these to be needed due to unstable ordering: https://github.com/apache/arrow-datafusion/actions/runs/8722139931/job/23927618449?pr=10114
alamb
approved these changes
Apr 18, 2024
| 12)--------------PlaceholderRowExec | ||
|
|
||
| query IIII | ||
| query IIII rowsort |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 #10113 .
Rationale for this change
What changes are included in this PR?
Coerce AVG accumulator to designated return type in case of columns with nulls.
Are these changes tested?
Yes, also a test is extended.
Are there any user-facing changes?
The query reported in the issue works now.