[BugFix] make max_by/min_by's output result column always nullable (backport #55116) #55132
Conversation
This file contains 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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
…55116) Signed-off-by: before-Sunrise <[email protected]> (cherry picked from commit c42afe2)
24 tasks
satanson
approved these changes
Jan 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why I'm doing:
max_by/min_by's output result column should be always nullable. for example, max_by(col1, col2), if col2's max value is still null, then even if col1 is not nullable, it must output null.
What I'm doing:
Fixes https://github.com/StarRocks/StarRocksTest/issues/9104
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: