bitadmiral

Thank you @anandgupta42 for the tip on getting the environment variables printed in the terminal. I did read that note in the documentation about setting environment variables in the shell...

After disabling all MS python-related extensions, restarting VS Code, and then re-enabling, I no longer see this `pythonTerminalEnvVarActivation` experiment available in my settings. While I'm not yet sure what my...

Without the `pythonTerminalEnvVarActivation` experiment, what will be the purpose of the `python.envFile` setting going forward?

It is not possible to execute a CREATE TABLE command when attaching a Glue catalog, either via its REST endpoint or "natively" using ENDPOINT_TYPE = 'GLUE'. This limitation seems to...

> It is not possible to execute a CREATE TABLE command when attaching a Glue catalog, either via its REST endpoint or "natively" using ENDPOINT_TYPE = 'GLUE'. > ... Just...

Does it succeed with a secret having **CHAIN** set explicitly to 'sso' when reading from an attached database where that database is the Glue Iceberg REST API? I'm referring to...

I'd like to add some additional diagnostic info for this issue. I get similar errors when running `CREATE TABLE ()` and with CTAS statements. It should be noted though that...

At first I thought we should see a HEAD request from DuckDB before attempting to create the table to see if the table exists already. The Glue Iceberg REST API...

Here is a line of code that seems to indicate a hidden option named `support_stage_create` is supported in the ATTACH statement: [irc_catalog.cpp#L457](https://github.com/duckdb/duckdb-iceberg/blob/2b5a4f5bc0858bfe9c30614bc779dace92a96d7d/src/storage/irc_catalog.cpp#L457) So this statement below does actually run without...

> I'm popping in because I'm noticing the same thing not eh error of "cannot parse missing string: location". I can write to a pre-existing iceberg table in the aws...