Catalogs Module

Overview

The Catalogs Module is responsible for managing data catalogs within the system.

Catalogs simplify data governance and execution management by serving as top-level logical containers for schemas, namespaces, and tables. Instead of configuring warehouses, routing modes, and execution capabilities individually for every data object, administrators can manage these configurations at the catalog level.

Within the system, catalogs define execution behaviors such as Iceberg REST API support, commit tracking, and maintenance operations. Capabilities assigned to a catalog are automatically applied across its underlying namespaces and data tables.

Catalog Management

This page displays a comprehensive list of all defined catalogs within the system.

From this interface, users can perform the following actions:

View all catalogs along with their current status, description, default warehouse mapping, and active capability badges.
Search, filter, and sort the catalog repository using the centralized search bar and table controls.
Switch between list and card views using the view toggles.
Create new catalogs via the slide-out panel ("Add Catalog") on the right.
Inspect details, manage namespaces, or delete existing catalogs using the row action menu (...).
Monitor whether a catalog is Active or Inactive across the platform ecosystem.

Catalog Attributes

Each catalog record consists of the following metadata fields:

Field	Description
Name	The unique identifier and display name for the catalog, shown along with its active capabilities badges (e.g., `Iceberg Rest`, `Commit`, `Maintenance`).
Description	Contextual information outlining the purpose of the catalog or its target department/team.
Default Warehouse	The target data warehouse assigned to execute queries and manage storage for this catalog.
Create Date	The exact timestamp denoting when the catalog was first registered in the system.
Update Date	The timestamp indicating when the catalog parameters or configurations were last modified.
Status	Indicates whether the catalog is currently `Active` or `Inactive` within the system ecosystem.

Key Considerations

Schemas and tables must belong to an active catalog to be accessible for query execution.
Disabling a catalog (Status set to Inactive) immediately hides its underlying namespaces from query routing.
Row actions (...) should be utilized to modify configurations or delete catalogs post-creation.