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
However it seems this issue apache/arrow-rs#2795 has been resolved and the fix merged a while back, and attempting the above steps without an AWS_REGION env var set still results in same error. Unsure whether user doc is wrong or there is another bug relating to AWS_REGION?
jeffrey:~/Code/arrow-datafusion/datafusion-cli$ export AWS_ACCESS_KEY_ID=****************
jeffrey:~/Code/arrow-datafusion/datafusion-cli$ export AWS_SECRET_ACCESS_KEY=****************
jeffrey:~/Code/arrow-datafusion/datafusion-cli$ export AWS_REGION=
jeffrey:~/Code/arrow-datafusion/datafusion-cli$ cargo run
Finished dev [unoptimized + debuginfo] target(s) in 0.10s
Running `/media/jeffrey/1tb_860evo_ssd/.cargo_target_cache/debug/datafusion-cli`
DataFusion CLI v14.0.0
❯ create external table test stored as parquet location 's3://tremendous-orange-fork/customer/part-0.parquet';
Execution("Generic S3 error: Missing region")
❯
The text was updated successfully, but these errors were encountered:
Describe the bug
When following steps from user guide for cli:
https://github.com/apache/arrow-datafusion/blob/fc669d5892954cbd2612a272314785758a7cb176/docs/source/user-guide/cli.md?plain=1#L154-L187
Cannot create a table as it states.
To Reproduce
Expected behavior
Be able to create a table from s3 and query it, per instructions in the user doc.
Additional context
User doc also states that
AWS_REGION
must be set as per:https://github.com/apache/arrow-datafusion/blob/fc669d5892954cbd2612a272314785758a7cb176/docs/source/user-guide/cli.md?plain=1#L162-L164
However it seems this issue apache/arrow-rs#2795 has been resolved and the fix merged a while back, and attempting the above steps without an
AWS_REGION
env var set still results in same error. Unsure whether user doc is wrong or there is another bug relating toAWS_REGION
?The text was updated successfully, but these errors were encountered: