-
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: resolveFromPlan when tblName.colName exists in having clause (#18349) #18434
planner: resolveFromPlan when tblName.colName exists in having clause (#18349) #18434
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
/merge |
/run-all-tests |
/merge |
@ti-srebot merge failed. |
/run-all-tests |
@ti-srebot merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
cherry-pick #18349 to release-4.0
What problem does this PR solve?
Issue Number: close #18384
Problem Summary:
What is changed and how it works?
What's Changed:
For SQL like
select a+1 from t having t.a
, we need to resolve it from the plan and select fields both.How it Works:
Related changes
Check List
Tests
Side effects
N/A
Release note
select a from t having t.a