-
Notifications
You must be signed in to change notification settings - Fork 42
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
error reading iceberg table #2603
Comments
This seems like an issue with |
I believe that this was addressed in #2718, which was released yesterday in 0.9.1. @djouallah let us know if this works or if you still have an issue or if you have any example datasets (or ways of producing data) that you think we should have integration tests for. |
getting new errors you can genereate iceberg tables using pyiceberg local |
Thanks! I'll definitely take a look at this on priority. Once we have a variety of datasets, we should be able to resolve most of the incompatibility issues with |
Just collecting some notes after looking at the notebook you posted @djouallah: glaredb.sql(""" select * from
iceberg_scan('/content/warehouse/default.db/taxi_dataset/metadata/00001-c13c72f3-6082-444c-9256-bea980ff7e0e.metadata.json') """) And the error:
It seems like glaredb (and duckdb) both expect to be pointed to the top level directory that contains the iceberg table, in this case
DuckDB has the same error (it's looking for the same file) so I imagine that there's something unexpected about this dataset or the way it's saved. My inspection of the pyiceberg api did not render anything fruitful yet, but I will look back into it. |
Fixes #2603 --------- Signed-off-by: Vaibhav <vrongmeal@gmail.com>
data can be read fine using duckdb
The text was updated successfully, but these errors were encountered: