Closed plbremer closed 5 months ago
Thanks, it does look like s3_output
was not properly trickled down to all underlying methods. Should be fixed by #2767. You can test it by installing the library via the branch:
pip uninstall awswrangler -y
pip install git+https://github.com/awslabs/aws-data-wrangler.git@fix/missing-s3-output
Thanks, it does look like
s3_output
was not properly trickled down to all underlying methods. Should be fixed by #2767. You can test it by installing the library via the branch:pip uninstall awswrangler -y pip install git+https://github.com/awslabs/aws-data-wrangler.git@fix/missing-s3-output
thanks for the super rapid fix
Describe the bug
running something like
will still cause awswrangler to write to its preferred default bucket
if it does not have access to its default bucket, then the query will not resolve
note that in the case where permissions exist, corresponding to the above image, the output is created as expected in the specified s3 thereafter
How to Reproduce
Give yourself an AWS IAM role that does not have permission to create buckets in an environment that does not have awswranglers default bucket already made. try to create an iceberg table. awswrangler will complain that the default bucket does not exist.
Expected behavior
No response
Your project
No response
Screenshots
No response
OS
mac 13.5 (22G74)
Python version
3.11.3
AWS SDK for pandas version
3.7.2
Additional context
No response