-
Notifications
You must be signed in to change notification settings - Fork 419
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
[python] tcp connect error reading from a public s3 bucket with {"anon": "true"}
#1554
Comments
Relating issues: Relating threads: |
I can certainly confirm that this still exists. This isn't a problem in the Python or Rust layer, but in fact a problem with object_store. Here's an example that reproduces it: use object_store::aws::AmazonS3Builder;
use object_store::ObjectStore;
use futures::stream::StreamExt;
#[tokio::main]
async fn main() -> deltalake::DeltaResult<()> {
// s3://coiled-datasets/h2o-delta/N_1e7_K_1e2/
let s3 = AmazonS3Builder::from_env()
.with_bucket_name("coiled-datasets")
.with_region("us-east-2")
.build()?;
let mut stream = s3.list(None).await?;
println!("Reading list stream");
while let Some(result)= stream.next().await {
println!("listed: {result:?}");
}
Ok(())
} Output
The origination seems to come from here. Basically the object_store crate does not accept the possibility of credentials missing and that being okay at the moment, so an upstream fix is going to need to be made. |
DeltaLake SDK does not support anonymous mode access (see: issue delta-io/delta-rs#1554) We throw an error if a user attempts to supply `anonymous=True`. --------- Co-authored-by: Jay Chia <[email protected]@users.noreply.github.com>
@j-bennet can you create an issue upstream in object store please |
Environment
Delta-rs version: 0.10.0
Binding: Python
Environment:
Bug
What happened:
Can't read a table from a public s3 bucket:
Error looks like this:
Setting
AWS_ENDPOINT_URL
doesn't help.What you expected to happen:
DeltaTable instance initialized.
How to reproduce it:
Code snippet above.
More details:
The text was updated successfully, but these errors were encountered: