AWS_S3_ALLOW_UNSAFE_RENAME="true"
in maybe_set_aws_credentials
incorrectly passed to pyarrow
#88
Labels
AWS_S3_ALLOW_UNSAFE_RENAME="true"
in maybe_set_aws_credentials
incorrectly passed to pyarrow
#88
Hi! In
maybe_set_aws_credentials
, theAWS_S3_ALLOW_UNSAFE_RENAME
is set totrue
. This causes a the following call, with no credentials provided, to fail:This call currently fails with the following error (full traceback at end):
The
read_deltalake
call should succeed, since I'm executing it on an EC2 instance that has an IAM role configured with permissions to my bucket. I've confirmed I can read this same table with polars:I am able to work around this temporarily by using path
s3a://my/deltatable
sincemaybe_set_aws_credentials
explicitly checks for thes3://
prefix (is this also a bug? it should probably check fors3a
ands3n
too?), but I'm pretty sure this is a bug related to how these credentials eventually make their way to pyarrow. I've included my package versions and full traceback below. If this is indeed a bug, I'm happy to try to write a fix.Traceback
Package Versions
Deltalake: 0.23.2 Dask-deltatable: 0.3.3 Pyarrow: 18.1.0
The text was updated successfully, but these errors were encountered: