-
Notifications
You must be signed in to change notification settings - Fork 0
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
Duckdb iceberg_scan
can read directly from metadata.json
#1
Comments
Nevermind, I dont think the above will work currently. Originally based the above on this comment duckdb/duckdb-iceberg#29 (comment) Looks like there are a few other issues with Here's the part I tried to change
Output and Error, (I change the warehouse path to /tmp/
|
Possibly related duckdb/duckdb-iceberg#38 Anyways, thanks for the great article! |
@kevinjqliu yeah, we had issues reading |
Here's what worked for me. I'm using the docker container used for pyiceberg integration tests ( I think the relevant changes are the in duckdb
Cheers. |
Thanks for the great article for Iceberg + DuckDB https://www.definite.app/blog/iceberg-query-engine
I just want to mention that Duckdb's
iceberg_scan
can read Iceberg table using its metadata.json file directly.Something like
So you can skip creating
version-hint.text
files entirely.Furthermore, Pyiceberg should always return a table's latest metadata location.
The text was updated successfully, but these errors were encountered: