-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-37098][SQL][3.0] Alter table properties should invalidate cache #34379
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
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #144582 has finished for PR 34379 at commit
|
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #144587 has finished for PR 34379 at commit
|
|
retest this please |
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
6c3781c to
2ae0a54
Compare
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #144601 has finished for PR 34379 at commit
|
|
Test build #144604 has finished for PR 34379 at commit
|
dongjoon-hyun
left a comment
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.
+1, LGTM.
|
Merged to branch-3.0. |
This PR backport #34365 to branch-3.0 ### What changes were proposed in this pull request? Invalidate the table cache after alter table properties (set and unset). ### Why are the changes needed? The table properties can change the behavior of wriing. e.g. the parquet table with `parquet.compression`. If you execute the following SQL, we will get the file with snappy compression rather than zstd. ``` CREATE TABLE t (c int) STORED AS PARQUET; // cache table metadata SELECT * FROM t; ALTER TABLE t SET TBLPROPERTIES('parquet.compression'='zstd'); INSERT INTO TABLE t values(1); ``` So we should invalidate the table cache after alter table properties. ### Does this PR introduce _any_ user-facing change? yes, bug fix ### How was this patch tested? Add test Closes #34379 from ulysses-you/SPARK-37098-3.0. Authored-by: ulysses-you <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
|
thank you @dongjoon-hyun |
This PR backport #34365 to branch-3.0
What changes were proposed in this pull request?
Invalidate the table cache after alter table properties (set and unset).
Why are the changes needed?
The table properties can change the behavior of wriing. e.g. the parquet table with
parquet.compression.If you execute the following SQL, we will get the file with snappy compression rather than zstd.
So we should invalidate the table cache after alter table properties.
Does this PR introduce any user-facing change?
yes, bug fix
How was this patch tested?
Add test