-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
planner: fix wrong behavior for != any() (#20058) #20062
planner: fix wrong behavior for != any() (#20058) #20062
Conversation
Signed-off-by: ti-srebot <[email protected]>
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. @wshwsh12 please fix the CI.
/run-all-tests |
/run-unit-test |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@ti-srebot merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@ti-srebot merge failed. |
/run-sqllogic-test-1 |
/run-sqllogic-test |
/run-all-tests |
cherry-pick #20058 to release-4.0
What problem does this PR solve?
Issue Number: close #20007
Problem Summary:
The result is unstable.
What is changed and how it works?
Proposal: xxx
What's Changed: Use max function instead of first_row function.
How it Works:
Related changes
Check List
Tests
Side effects
Release note