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-33688][SQL] Migrate SHOW TABLE EXTENDED to new resolution framework #30645
Conversation
@cloud-fan @imback82 @HyukjinKwon Please, review this PR. |
Kubernetes integration test starting |
Test build #132364 has finished for PR 30645 at commit
|
Kubernetes integration test status success |
@cloud-fan Don't think the failed test are related to the changes:
|
retest this please |
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
@@ -3199,13 +3199,17 @@ class AstBuilder extends SqlBaseBaseVisitor[AnyRef] with SQLConfHelper with Logg | |||
} | |||
|
|||
/** | |||
* Create a [[ShowTableStatement]] command. | |||
* Create a [[ShowTableExtended]] command. | |||
*/ | |||
override def visitShowTable(ctx: ShowTableContext): LogicalPlan = withOrigin(ctx) { |
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.
nit: should we update sqlbase.g4
so that this becomes visitShowTableExtended
?
Kubernetes integration test starting |
Kubernetes integration test status success |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #132376 has finished for PR 30645 at commit
|
Test build #132383 has finished for PR 30645 at commit
|
retest this please |
Test build #132410 has finished for PR 30645 at commit
|
thanks, merging to master! |
What changes were proposed in this pull request?
ShowTableStatement
ShowTableExtended
forSHOW TABLE EXTENDED
.This PR is the first step of new V2 implementation of
SHOW TABLE EXTENDED
, see SPARK-33393.Why are the changes needed?
This is a part of effort to make the relation lookup behavior consistent: SPARK-29900.
Does this PR introduce any user-facing change?
The changes should not affect V1 tables. For V2, Spark outputs the error:
How was this patch tested?
By running
SHOW TABLE EXTENDED
tests: