Thijs
Thijs
Yea that Avro file is invalid, it's missing required fields. It's also missing fields in the avro's key-value metadata (https://iceberg.apache.org/spec/#manifests), but we don't currently check those anyways. But the `content`...
It's whoever wrote the manifest file. But as said, this is likely our issue, because we're assuming the manifest files have the same `format-version` as the `metadata.json` file, because we...
Does this meet your needs? https://github.com/duckdb/ducklake/pull/175
See #45
Hmm, that is strange, I assume it's related to your OS, presumably being Windows? I would advice to attach the catalog instead of querying the table directly, I doubt that...
I don't think you have `LOAD ICEBERG;` in your session, if you are hitting `Binder error for unrecognized storage type "iceberg"`
You might need to do a `FORCE INSTALL ICEBERG;`, as a new version of the 1.2.2 release was pushed today (4~ hours ago)
I don't, I'm not that versed on the s3/aws request signing, but it looks like there are config settings from either the `/v1/config` or `/v1/namespaces/{namespace}/tables/{table}` `storage-credentials` result that are not...
That's not our error, that's an error by the REST catalog. When we implement a retry mechanism this shouldn't surface (or at least in less scenarios) to the user
Please post the full compilation error, to provide proper context. Likely what's wrong here is DUCKDB_API missing in one or more places for the definitions of the classes/methods