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

binder error when directly scanning metadata file #23

Open
xiaom opened this issue Oct 25, 2023 · 2 comments
Open

binder error when directly scanning metadata file #23

xiaom opened this issue Oct 25, 2023 · 2 comments

Comments

@xiaom
Copy link

xiaom commented Oct 25, 2023

Hey,

I am encountering an issue while trying to scan metadata files directly from an Iceberg table located in S3.

Here are the details:

  • Data Source: Iceberg table in S3, written by Flink with AWS Glue Catalog.
  • DuckDB Version: v0.9.1

Query

select * from  iceberg_scan('s3://<...>/metadata/00136-4330ee25-0db5-42a4-8230-035d739f76e7.metadata.json') limit 1;

Error:

Binder Error: Table "iceberg_scan_deletes" does not have a column named "file_path"

Would appreciate any insights or suggestions on what could be causing this issue. Thank you!

@Fokko
Copy link
Contributor

Fokko commented Nov 29, 2023

Could you double-check the manifest file to see if the path is in there? This can be done easily using avro-tools tojson manifest-file.avro.

@lamb-russell
Copy link

i have a similar example in this notebook

key part is near the bottom
image

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

3 participants