Uh oh!
There was an error while loading. Please reload this page.
[SPARK-33688][SQL] Migrate SHOW TABLE EXTENDED to new resolution framework - #30645
[SPARK-33688][SQL] Migrate SHOW TABLE EXTENDED to new resolution framework#30645MaxGekk wants to merge 5 commits into
Conversation
MaxGekk
commented
Dec 7, 2020
@cloud-fan@imback82@HyukjinKwon Please, review this PR. |
SparkQA
commented
Dec 7, 2020
Kubernetes integration test starting |
SparkQA
commented
Dec 7, 2020
Test build #132364 has finished for PR 30645 at commit
|
SparkQA
commented
Dec 7, 2020
Kubernetes integration test status success |
MaxGekk
commented
Dec 7, 2020
@cloud-fan Don't think the failed test are related to the changes: |
cloud-fan
commented
Dec 7, 2020
retest this please |
| * Create a [[ShowTableStatement]] command. | ||
| * Create a [[ShowTableExtended]] command. | ||
| */ | ||
| override def visitShowTable(ctx: ShowTableContext): LogicalPlan = withOrigin(ctx) { |
There was a problem hiding this comment.
nit: should we update sqlbase.g4 so that this becomes visitShowTableExtended?
SparkQA
commented
Dec 7, 2020
Kubernetes integration test starting |
SparkQA
commented
Dec 7, 2020
Kubernetes integration test status success |
SparkQA
commented
Dec 7, 2020
Kubernetes integration test starting |
SparkQA
commented
Dec 7, 2020
Kubernetes integration test status success |
SparkQA
commented
Dec 7, 2020
Test build #132376 has finished for PR 30645 at commit
|
SparkQA
commented
Dec 7, 2020
Test build #132383 has finished for PR 30645 at commit
|
cloud-fan
commented
Dec 8, 2020
retest this please |
SparkQA
commented
Dec 8, 2020
Test build #132410 has finished for PR 30645 at commit
|
cloud-fan
commented
Dec 8, 2020
thanks, merging to master! |
What changes were proposed in this pull request?
ShowTableStatementShowTableExtendedforSHOW 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 EXTENDEDtests: