-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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-33787][SQL][3.1] Add the purge
parameter to dropPartition()
of SupportsPartitionManagement
#30821
Conversation
…log/SupportsAtomicPartitionManagement.java Co-authored-by: John Bampton <jbampton@users.noreply.github.com>
…log/SupportsAtomicPartitionManagement.java Co-authored-by: John Bampton <jbampton@users.noreply.github.com>
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #132942 has finished for PR 30821 at commit
|
jenkins, retest this, please |
Kubernetes integration test starting |
Kubernetes integration test status success |
Test build #132953 has finished for PR 30821 at commit
|
What changes were proposed in this pull request?
purge
todropPartition()
inSupportsPartitionManagement
anddropPartitions()
inSupportsAtomicPartitionManagement
.command
to V2 exec node and further to catalog implementations.SupportsPartitionManagement
andSupportsAtomicPartitionManagement
interfaces.dropTable
.Why are the changes needed?
The sql statement
ALTER TABLE .. DROP PARTITION
allows to specify thePURGE
flag but it is ignored by v2 implementation. We should propagate it at least toSupportsPartitionManagement
and toSupportsAtomicPartitionManagement
, and let to implementations of those interface decide how to support it.Does this PR introduce any user-facing change?
Should not.
How was this patch tested?
By running new UT: