add support to configure anonymous in s3 clients #2323
+81
−3
Conversation
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
Fokko
reviewed
Aug 12, 2025
There was a problem hiding this comment.
Thanks @gmweaver for adding this 🙌
Probably we want to add this to the docs as well: https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/configuration.md#s3
Do you know if there is a PyArrow equialent? If so, it would be nice to add that option as well.
pyarrow has a similar config updated the PR to include. |
gmweaver
changed the title
|
@gmweaver Thanks for being on top of this, could you run |
|
@Fokko sorry missed the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rationale for this change
Currently, it is not possible to configure
anonymousin the underlyings3fsclient (Falseby default).Resolves #2126
Are these changes tested?
Yes, unit tests added to confirm the setting is used when the property is set.
Are there any user-facing changes?
Yes, users can now set the property
s3.anonymousto True to enable. If not set, the behavior will be the same as it currently is.