-
Notifications
You must be signed in to change notification settings - Fork 16
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
Delta read on GCS seems to point to S3 instead #97
Comments
@junhl I am experiencing this issue as well - looks like the Delta extension in v1.1.0 is accidentally pointing to S3 instead of GCS. NOTE: downgrading to version 1.0.0 fixed the problem for me. |
Thanks @stele-and-rivers-001 - I also confirm it is working in 1.0.0 - looks like there was an accidental change as you said in 1.1.0. |
I faced the same problem in version 1.1.2, is there any update for this problem ? |
Experiencing the same issue and can confirm it is working in 1.0.0. |
Same issue for version 1.1.3. |
I have delta table on GCS and tried reading it with Delta extension of DuckDB
Using python library, version 1.1.0:
This leads to
The error message indicates it tried as S3 instead of GCS, which wouldn't work.
The text was updated successfully, but these errors were encountered: