Mark

For S3 connectivity, as of #5419 DuckDB should also correctly interpret environment variables such as `AWS_ACCESS_KEY_ID ` and `AWS_SECRET_ACCESS_KEY ` which can be used for this purpose as well.

Implemented in #9651

This issue should actually be closed as casting from strings to complex types has been implemented: ```sql D select '[1, 2, 3]'::INT[] AS l; ┌───────────┐ │ l │ │ int32[]...

I’m happy to have another look at this issue but we haven’t been able to reproduce it ourselves. Do you have a reproducible example you could share?

Could you share the full error you receive? Or is it only `Resource temporarily unavailable`? I suspect this might be file-system dependent and have to do with file locks.

Could you share the database file, or does copying/moving the database file resolve the issue?

Thanks for the report! Looks like this file uses the `DELTA_BYTE_ARRAY` encoding. I will have a look to see if we can support this.

Should all be implemented on #5457 now

Could you confirm the issue is still a problem with the latest version of DuckDB (v0.8.1)?

As per https://github.com/duckdb/duckdb/pull/9126, you can access the extra key/value information using the `parquet_kv_metadata` function: ```sql D from parquet_kv_metadata('test.parquet'); ┌──────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ key │ value │ │ blob │ blob │ ├──────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤...