Skip to main content

Catalog

The Catalog gives users a view of the data assets available in their workspace — tables, schemas, ownership, lineage, and access permissions — all in one place.

The supported catalog and current limitations are documented in the canonical Data Catalog assessment. In the assessed workspace, only the Superset-registered delta catalog is supported in this UI.

Services Behind This Feature​

ServiceRole
BFF APIRoutes requests from the Cogrion UI to Superset, DataHub, Ranger, and Trino-backed services.
DatahubStores descriptions, tags, structured properties, and lineage; it does not determine the top-level catalog list.
SupersetData exploration and visualization
TrinoQuery engine
RangerProvides the access control layer — permissions visible in the catalog are enforced here at query time.
Hive MetastoreStores schemas and tables for the current Delta and Hive connectors.

What a Table Detail Page Shows​

When a user opens a specific table in the Catalog, they see:

TabContent
OverviewColumn names, data types, DataHub tags, and descriptions
Sample dataA preview of actual row data from the table (fetched via Trino)
PermissionsDirect and inherited Ranger permissions
HistoryDelta table history
LineageUpstream and downstream DataHub relationships, when matching lineage metadata exists
QualityResults from data quality checks run against the table

Lineage​

The Catalog reads lineage from DataHub. It appears only when a producer emits lineage using the same canonical dataset identity that the Catalog requests. Current deployment source does not establish complete producer coverage, and the reviewed UI constructs a different lineage URN from its metadata URN. See DATA-CAT-001.

Go Deeper​