-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Fixing aliases for GLOBAL IN #64517
Fixing aliases for GLOBAL IN #64517
Conversation
This is an automated comment for commit 84d2bbc with description of existing statuses. It's updated for the latest CI running ⏳ Click here to open a full report in a separate page
Successful checks
|
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.
Please, add a test from the issue description.
@@ -6566,7 +6578,8 @@ ProjectionNames QueryAnalyzer::resolveExpressionNode(QueryTreeNodePtr & node, Id | |||
scope.scope_node->formatASTForErrorMessage()); | |||
|
|||
auto & table_node = node->as<TableNode &>(); | |||
result_projection_names.push_back(table_node.getStorageID().getFullNameNotQuoted()); | |||
if (result_projection_names.empty()) |
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.
Just curious: when can it be non-empty?
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.
In the scenario I saw, we can resolve identifier x alias y
as TableNode (by alias), and in this case, at first, alias would be added to projection names, and then the storage name.
Cloud does not use GLOBAL IN; backport still makes sense to simplify other backports. |
In stress tests, probably we stuck in distributed async inserts.
|
…e5fcfb2013eabcf38be007840acdd Cherry pick #64517 to 24.4: Fixing aliases for GLOBAL IN
…e5fcfb2013eabcf38be007840acdd Cherry pick #64517 to 24.5: Fixing aliases for GLOBAL IN
Backport #64517 to 24.5: Fixing aliases for GLOBAL IN
Backport #64517 to 24.4: Fixing aliases for GLOBAL IN
…e5fcfb2013eabcf38be007840acdd Cherry pick #64517 to 24.3: Fixing aliases for GLOBAL IN
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix the
Expression nodes list expected 1 projection names
andUnknown expression or identifier
errors for queries with aliases toGLOBAL IN.
Fixes #64445