Tom Ebergen

Hi, Thanks for filing the issue. I don't think this is a bug, if you have vended credentials, a custom s3 endpoint should not overwrite the credentials returned via vended...

Do you know what the response is when creating a table? Are you including a `"location" : "s3://polardb/"` key value in the `metadata`. That's the only thing I can think...

Looking at this again, I realized I could add support for a `default-base-location`, however, upon further inspection, I see that the Catalog configuration json you posted does not follow the...

Hi @ibenian, Have you been able to reproduce this issue with a small example? This seems to be a common issue. Can you describe a bit more the properties of...

Thank you for reporting this. Can you provide the following details? - what query causes this error? - What version of DuckDB are you using? And what client? - Do...

Hi @elventear, So I have been looking into this to try and reproduce without having to actually create an enormous table, and have had no luck. I have questions about...

Hmmm, very interesting, because it seems like s3tables does not support operations on a table with a metadata.json over 5MB, see https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-open-source.html (in the Limitations section) Interesting that other clients...

Hi @elventear, I have chatted with an AWS representative and it seems like the issue you are seeing is indeed that the metadata.json is too large and s3tables will not...

Forgot to mention, you can use the get-table aws cli command to get the metadata.json, then directly read from that in duckdb ``` aws s3tables get-table --table-bucket-arn arn:aws:s3tables:{region}:{account-id}:bucket/{table_bucket_name} --namespace {namespace}...

@din14970 have you enabled external engines to access data in s3 locations as described in [this comment](https://github.com/duckdb/duckdb-iceberg/issues/454#issuecomment-3330440767)? That is the main reason I can think of as to why you...