-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-37888][SQL][TESTS] Unify v1 and v2 DESCRIBE TABLE tests
#36912
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
Conversation
DESCRIBE TABLE testsDESCRIBE TABLE tests
|
A major problem in #35265 is how to unify the v1 and v2 DESCRIBE TABLE command. I'm OK to unify the tests first, and let's unify the commands in a later PR. |
|
Merging to master. Thank you, @cloud-fan for review. |
| Row("Database", "ns", ""), | ||
| Row("Table", "table", ""), | ||
| Row("Last Access", "UNKNOWN", ""), | ||
| Row("Created By", "Spark 3.4.0-SNAPSHOT", ""), |
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 should filter out this row as well, otherwise we need to keep updating this test when making a new release. cc @MaxGekk
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.
Will do in another PR for DESCRIBE TABLE 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.
Next time, let's address comments immediately. We missed fixing it in the next PR...
What changes were proposed in this pull request?
DESCRIBE TABLEparsing tests toDescribeRelationParserSuite.DESCRIBE TABLEtests into one traitorg.apache.spark.sql.execution.command.DescribeTableSuiteBase, and put datasource specific tests to thev1.DescribeTableSuiteandv2.DescribeTableSuite.The changes follow the approach of #30287.
Closes #36671.
Why are the changes needed?
DESCRIBE TABLEtests for both DSv1/Hive DSv1 and DSv2Does this PR introduce any user-facing change?
No.
How was this patch tested?
By running the modified test suites:
and new test suites: