`USE <database>` fails with `ATTACH`-ed AWS S3 tables.

[steinwaywhw]

What happens?

I couldn't get USE <database> to work with an ATTACH-ed S3 Table.

Setup:

1. an AWS account with a S3 Table bucket, with the "AWS analytic integration" thing enabled so that the S3 table pops up in AWS LakeFormation as a catalog.
2. Have duckdb 1.4.1 available with all the necessary extensions.
3. You've logged in to the correct AWS account/profile using your AWS cli.

CREATE OR REPLACE SECRET (TYPE s3, PROVIDER credential_chain);

ATTACH IF NOT EXISTS '<aws_account_id>:s3tablescatalog/<bucket_name>'
  AS datalake (ENDPOINT_TYPE glue, TYPE iceberg);

USE datalake;

Problem:

the USE datalake statement fails

Catalog Error: SET schema: No catalog + schema named "datalake" found.

Additional info:

• If I do SHOW ALL TABLES, I can see I have many such records: database=datalake, schema=someschema, table=sometables.
• If I do USE datalake.someschema, it works.

I don't know what I did wrong here. Happy to provide more information if needed but I'm a bit clueless.

To Reproduce

See above.

OS:

MacOS M3

DuckDB Version:

1.4.1

DuckDB Client:

CLI

Hardware:

No response

Full Name:

Steinway Wu

Affiliation:

Individual

Did you include all relevant configuration (e.g., CPU architecture, Linux distribution) to reproduce the issue?

• Yes, I have

Did you include all code required to reproduce the issue?

• Yes, I have

Did you include all relevant data sets for reproducing the issue?

Not applicable - the reproduction does not require a data set

[Tishj]

Thanks, this is not the place for duckdb-iceberg issues, that has its own repository and issue tracker: https://github.com/duckdb/duckdb-iceberg/issues

@szarnyasg could you move this there?

[Tishj]

As for the problem at hand, that error usually shows up when the default schema that gets returned by the catalog doesn't return a valid value.
It will attempt to get the schema and if that fails, it treats the datalake portion as a schema, not as a catalog, at which point it throws this error, because no schema exists by the name datalake

[Tishj]

I believe the default schema that we return is main, I believe we have an ATTACH option to override this, if not, we should add that 👍

[steinwaywhw]

I see. Thank you for all the context!

[Tishj]

I've added the missing attach option, but as a workaround specifying the schema in the USE should work:

USE  catalog.schema;

But you already knew that 👍