-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Spark] Support show tblproperties and update catalog for clustered table #3271
[Spark] Support show tblproperties and update catalog for clustered table #3271
Conversation
293547e
to
795a95e
Compare
795a95e
to
4e65a35
Compare
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.
Looks good to me!
// This is necessary because the [[SparkThreadLocalForwardingThreadPoolExecutor]] | ||
// retains a reference to the SparkContext. Without resetting, the new test suite would | ||
// reuse the same SparkContext from the previous suite, despite it being stopped. |
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.
Can we also point out that this is mainly for the UpdateCatalogHook background thread to have a new SparkContext to avoid access-after-stop issue between suites?
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.
Sure, added a comment.
46f82cc
to
8fc040c
Compare
5aee0cd
to
97c1ef2
Compare
c4bc884
to
2b5f432
Compare
Which Delta project/connector is this regarding?
Description
Support show tblproperties for clustered table, and support updating the clustering column properties in the catalog. Remove table properties from describe detail's output since that's using the properties from metadata.
How was this patch tested?
Add verification for table properties, describe detail, and catalog table in verifyClusteringColumns.
Does this PR introduce any user-facing changes?
No