Skip to content

Error on catalog Iceberg REST : system namespace does not exist #25829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
baptistegh opened this issue May 20, 2025 · 1 comment
Open

Error on catalog Iceberg REST : system namespace does not exist #25829

baptistegh opened this issue May 20, 2025 · 1 comment
Labels
iceberg Iceberg connector

Comments

@baptistegh
Copy link

I have a strange behavior with my JDBC/ODBC clients on Trino 475.

I use a Iceberg REST Catalog (lakekeeper).

Some of my Trino clients uses some SQL to show existing tables and views.

But I found that when a request on <catalog>.information_schema.tables is filtered, a request is executed on the Iceberg catalog but it does not know the system namespace.

Exemple:

This is working fine:

select * from <iceberg_catalog>.information_schema.tables;

This does not work:

select * from <iceberg_catalog>.information_schema.tables where table_catalog LIKE '<iceberg_catalog>'

I don't understand why trino is requesting the catalog to list tables/views under the system namespace.

Logs from Lakekeeper (iceberg rest)

GET /catalog/v1/<uid_warehouse>/namespaces/system/tables
GET /catalog/v1/<uid_warehouse>/namespaces/system/views

If I don't filter the request, I don't see those 2 requests in Lakekeeper logs.

@baptistegh
Copy link
Author

Even a limit does not work

Exemple:

select * from <iceberg_catalog>.information_schema.tables limit 200;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
iceberg Iceberg connector
Development

No branches or pull requests

2 participants