Thành Đạt
04/29/2026, 7:57 AMThành Đạt
04/29/2026, 7:57 AMRocky
04/29/2026, 7:58 AMdefault_catalog alongside your external catalogs (e.g., hive_catalog, iceberg_catalog) directly in the database explorer tree.
2. Enable Catalog Discovery for MySQL Clients
If you are using the MySQL driver or an older version of DBeaver, StarRocks (v3.3+) supports a feature that allows MySQL-compatible clients to "discover" external catalogs as if they were databases.
* StarRocks Configuration:
Ensure your StarRocks cluster has external catalog discovery enabled for metadata queries. While this is increasingly the default behavior, you can verify your catalogs are visible by running:
sql
SHOW CATALOGS;
If you have the USAGE privilege on these catalogs, DBeaver's metadata crawler should be able to list them if you check the "Show all databases" option in the DBeaver connection's "Global Filters" or "Connection Settings."
3. Manual Workaround (Older Versions)
If your DBeaver tree still only shows the default_catalog, you can still access external catalogs via the SQL Editor or by manually switching the session context:
* Switching Catalog in Session:
Run this in a script to point DBeaver's current session to an external catalog:
sql
SET CATALOG <external_catalog_name>;
* Direct Access:
You can always query any catalog without switching by using the full path:
sql
SELECT * FROM catalog_name.database_name.table_name;
Summary Tip: If you don't see the StarRocks specific driver in your DBeaver version, update to the latest DBeaver 25.x or 26.x version, as the official StarRocks plugin was specifically enhanced to solve the catalog-visibility issue you's common in the tree view.
References
• sql-reference/sql-statements/Catalog/SHOW_CATALOGS.md
• data_source/catalog/catalog_overview.md
• sql-reference/sql-statements/Database/SHOW_DATABASES.md
• data_source/catalog/jdbc_catalog.md
• table_design/table_design.md
• data_source/catalog/default_catalog.md