-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why not use the profile name when initialising the S3FileSystem class? #1207
Comments
Hello, I am interested in this, do I need to tag the person who will assign this task to me? |
@wudihero2 assigned to you :) |
Hi folks, I was under the impression that this was something that would need to be addressed in PyArrow S3FileSystem. Please see @HonahX 's earlier comment: Previous issue on same topic: #570 On that note, I'm in favor of keeping this issue open since this is a frequent question from the community, until we are able to find a solution by perhaps working with the Arrow community. |
#1104 (comment) |
Hi all, I checked the code of pyarrow and found that the profile_name parameter is not currently supported. The s3.* related parameters are indeed not suitable for supporting profile_name. It would be great if we could work with the Arrow community to find a solution! This package is great and can help me use iceberg for my current job, thank you !! |
Question
Hi,
In #922 standardize some AWS credential names, but I am confused why not use below code to use aws profile name at pyiceberg.io.fsspec.py?
It supports the use of AWS profile names like `glue.profile-name' as in the following code at pyiceberg.catalog.glue.py
Maybe it would be a better improvement if we could use profile name or is there some concern I haven't considered?
The text was updated successfully, but these errors were encountered: