Skip to content
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

Open
junhl opened this issue Sep 18, 2024 · 5 comments
Open

Delta read on GCS seems to point to S3 instead #97

junhl opened this issue Sep 18, 2024 · 5 comments

Comments

@junhl
Copy link

junhl commented Sep 18, 2024

I have delta table on GCS and tried reading it with Delta extension of DuckDB

Using python library, version 1.1.0:

with duckdb.connect() as con:
    con.execute(
        """
        CREATE SECRET (
          TYPE GCS,
          KEY_ID 'SOME_KEY',
          SECRET 'SOME SECRET'
        )
        """
    )
    results = con.execute("select col1, col2 from delta_scan('gs://some-bucket/some-table')").fetch_df()

This leads to

duckdb.duckdb.IOException: IO Error: Hit DeltaKernel FFI error (from: While trying to read from delta table: 'gs://some-bucket/some-table/'): Hit error: 8 (ObjectStoreError) with message (Error interacting with object store: Generic S3 error: Error after 10 retries in 4.432062125s, max_retries:10, retry_timeout:180s, source:error sending request for url (https://s3..amazonaws.com/some-bucket/some-table/_delta_log/_last_checkpoint))

The error message indicates it tried as S3 instead of GCS, which wouldn't work.

@samereed
Copy link

samereed commented Sep 19, 2024

@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.

@junhl
Copy link
Author

junhl commented Sep 19, 2024

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.

@Marcus-Holanda777
Copy link

I faced the same problem in version 1.1.2, is there any update for this problem ?

@mvanma
Copy link

mvanma commented Nov 27, 2024

Experiencing the same issue and can confirm it is working in 1.0.0.

@patrickpio
Copy link

Same issue for version 1.1.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants