Spark: Support Bulk deletion in expire-snapshots if fileIO allows #5412
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.
In #4052, S3 fileIO now implement a new interfaces to support S3 batch deletion, this PR introduce it for Spark expire-snapshots procedure to conditionally support delete files in batch if underlying fileIO supports it (if implements
SupportsBulkOperationsinterface and currently only S3FileIO support such)It default to use S3 batch deletion if fileIO is supported in catalog, allow for customization with
bulkDeleteWithmethodbulkDeleteconsumer function because it only take single file name at a time instead of a iterableSimilar to #5373 but for expire-snapshots procedure, relate to #4012
CC @rdblue , @danielcweeks, @amogh-jahagirdar, @szehon-ho