Spark 4.1: Add Spark REST_CATALOG_PURGE property to delegate DROP TABLE PURGE to REST catalogs#17186
Open
jackylee-ch wants to merge 1 commit into
Open
Conversation
…LE PURGE to REST catalogs Backport of apache#15614 to Spark 4.1. Adds the `rest-catalog-purge` catalog property. When enabled and the configured catalog is a REST catalog, Spark delegates DROP TABLE PURGE to the catalog (sending purgeRequested=true) instead of performing client-side file deletion. Defaults to false, so non-REST catalogs and existing behavior are unaffected.
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #15614 to Spark 4.1.
Adds the
rest-catalog-purgecatalog property. When enabled and the configured catalog is a REST catalog, Spark delegatesDROP TABLE ... PURGEto the catalog (sendingpurgeRequested=true) instead of performing client-side file deletion. Defaults tofalse, so non-REST catalogs and existing behavior are unaffected.This is a clean backport with no logic changes from the Spark 3.5 implementation. Companion to #17185 (Spark 4.0).