-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-30420][SQL][FOLLOWUP] Remove statement logical plans for namespace commands #27125
Conversation
cc: @cloud-fan |
Test build #116278 has finished for PR 27125 at commit
|
thanks, merging to master! |
DescribeNamespace(catalog, ns, extended) | ||
|
||
case ShowNamespacesStatement(NonSessionCatalogAndNamespace(catalog, ns), pattern) => | ||
ShowNamespaces(catalog, ns, pattern) |
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.
We missed the fallback to the v1 ShowDatabasesCommand
.
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.
Let me check, thanks.
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.
@cloud-fan could you clarify on the fallback?
"show databases" and "show namespaces" were merged by #26006 and both are handled by v2 ShowNamespacesExec
.
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.
Ah I misremember that. So we forgot to add a migration guide for the schema change... (databaseName -> namespace) Anyway it's too late now, let's catch schema changes in the following development work.
What changes were proposed in this pull request?
This is a follow-up to address the following comment: #27095 (comment)
Currently, a SQL command string is parsed to a "statement" logical plan, converted to a logical plan with catalog/namespace, then finally converted to a physical plan. With the new resolution framework, there is no need to create a "statement" logical plan; a logical plan can contain
UnresolvedNamespace
which will be resolved to aResolvedNamespace
. This should simply the code base and make it a bit easier to add a new command.Why are the changes needed?
Clean up codebase.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests should cover the changes.