Harel Efraim
Harel Efraim
I think that having a member of HashMap instead of extending HashMap would address the issue. @JsonAnyGetter and @JsonAnySetter are designed for this exactly. Like @FatCash suggested, there could be...
This is related to issues 6146 and 5515
@rustyconover - Thank you for this PR and #50. I have access to Iceberg tables on AWS Glue and can help testing this feature. Is it possible to provide a...
I tested this branch on AWS with several Iceberg tables. This query pattens works fine: select * from iceberg_scan('users', catalog_type="glue", region="us-east-1", database_name="test_iceberg"); Hoping to see it in the upcoming 0.10.3...
I ran into similar issue using AWS with Glue as the catalog for Iceberg. The metadata files stored in S3 are of the following pattern: 00000-0b4430d2-fbee-4b0d-90c9-725f013d6f82.metadata.json 00001-6e3b4909-7e6b-486f-bf81-b1331eba3ac8.metadata.json I suspect Glue...
For Java iceberg users out there, I found a solution to retrieve the latest metadata without having to query the catalog directly. Once you load the table from the catalog,...
Yes, DuckDB 0.9.2 with Iceberg is working for me on the following setups: a. AWS S3 + AWS Glue b. MinIO + Nessie
You can use WITH clause instead of alias to define both t1 and t2.
Hi, I would first suggest to execute the query with 'explain analyze' and post the results here. The cause might be issue #2, where more parquet files are scanned than...
I got the same problem when upgrading from 1.3.0 to 1.3.1 DuckDB without the extension does not exhibit the same issue.