Loading polars.LazyFrame from S3 via PolarsParquetIOManager fails with "Generic S3 error: Missing bucket name" #22079
Replies: 2 comments
-
For the time being, I've been able to successfully patch this issue by doing the following:
to
where
|
Beta Was this translation helpful? Give feedback.
-
It looks like there is still a bug here, it looks like the read and write clients expect different arguments in storage_options and there is no way to unify them. The write client expects things like: |
Beta Was this translation helpful? Give feedback.
-
I'm trying to pass a polars.LazyFrame between two assets with code that roughly looks like so (omitting details in order to get a minimal reproducible example):
The
upstream
asset materializes and stores to S3 fine. However, calling.collect()
indownstream
fails with:I was hoping that adding an IO manager will help abstract away the bucket name / file location, but surprisingly this isn't working. Is there anything I could be missing in this setup?
Beta Was this translation helpful? Give feedback.
All reactions