Catalog management properties#

The following properties are used to configure catalog management.

All properties described in this page are defined as follows, depending on the deployment type:

  • Kubernetes: In the additionalProperties section of the the top-level coordinator and worker nodes in the values.yaml file.

catalog.management#

  • Type: string

  • Allowed values: static

  • Default value: static

When set to static, Trino reads catalog property files and configures available catalogs only on server startup.

When you drop a catalog that uses connectors capable of reading from HDFS, such as the Hive connector, Iceberg connector, Delta Lake connector, and Hudi connector connectors, some resources may not be fully released. Restart the coordinator and workers after dropping these catalogs to ensure proper cleanup.

The complete CREATE CATALOG query is logged and visible in the Starburst Enterprise web UI. It is strongly recommended to use a secrets manager rather than pass any credentials in plain text.

catalog.config-dir

  • Type: string

  • Default value: etc/catalog/

Requires catalog.management to be set to static. The directory with catalog property files.

catalog.disabled-catalogs

Requires catalog.management to be set to static. Comma-separated list of catalogs to ignore on startup.

catalog.read-only

  • Type: string

  • Default value: false

If true, existing catalog property files cannot be removed with DROP CATALOG, and no new catalog files can be written with identical names with CREATE CATALOG. As a result, a coordinator restart resets the known catalogs to the existing files only.