Repository navigation
feat: add implicit s3:DeleteObject grant for s3tables:DeleteTable - #211
Merged
harshavardhana merged 2 commits intoDec 13, 2025
Merged
Conversation
Add implicit permission so that s3tables:DeleteTable also grants s3:DeleteObject. This enables table purging (DROP TABLE ... PURGE) to delete underlying data files in the table's storage location. This is needed because Spark's DROP TABLE ... PURGE performs client-side deletes rather than using purgeRequested=true to let the catalog handle deletion. This workaround grants the necessary privilege until the issue is fixed in Spark/Iceberg upstream. References: - apache/iceberg#14743 - apache/iceberg#11023
harshavardhana
approved these changes
Dec 13, 2025
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
2 participants
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.
Summary
s3tables:DeleteTablealso grantss3:DeleteObjectDROP TABLE ... PURGE) to delete underlying data files in the table's storage locationBackground
When using Spark's
DROP TABLE ... PURGE, the operation fails because users withs3tables:DeleteTablepermission don't have thes3:DeleteObjectpermission needed to delete the underlying data files.This is a workaround for a Spark/Iceberg issue where
DROP TABLE ... PURGEperforms client-side deletes rather than usingpurgeRequested=trueto let the catalog handle deletion server-side.References
RCK fix