You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Documentation for s3.profile-name and client.profile-name is potentially misleading / vague #3066
Issue:
In #2948s3.profile-name and client.profile-name were introduced as new configuration parameters. These 2 parameters are only implemented for Fsspec backend so far. In the documentation (see mkdocs/docs/configuration.md) it gives the impression that these 2 parameters are supported generally (or more specifically also for PyArrow backend, where it is not implemented yet - see #3065 ).
Suggested fix:
There should be a remark in the documentation (see mkdocs/docs/configuration.md ) of s3.profile-name and client.profile-name stating the Fsspec backend must be used (or py-io-impl must be set to pyiceberg.io.fsspec.FsspecFileIO) for them to work.
Willingness to contribute
I can contribute a fix for this bug independently
I would be willing to contribute a fix for this bug with guidance from the Iceberg community
I cannot contribute a fix for this bug at this time
Activity
thomas-pfeiffer commentedon Feb 23, 2026
I created PR #3085 to fix this documentation issue. @stats-dev & @kevinjqliu Could you please take a look at it and provide your feedback?
Documentation `s3.profile-name` and `client.profile-name` (#3085)
Documentation `s3.profile-name` and `client.profile-name` (apache#3085)