Omni Pre - Datahub — ContextQMD

Overview

The omni module ingests metadata from the Omni BI platform into DataHub. It is intended for production ingestion workflows and supports the following:

Folders (as Containers), Dashboards, and Chart tiles
Semantic layer: Models, Topics, and Views with schema fields (dimensions and measures)
Physical warehouse tables with upstream lineage stitched to existing DataHub entities
Column-level (fine-grained) lineage from semantic view fields back to warehouse columns
Ownership propagated from the Omni document API

Lineage is emitted as a five-hop chain:

Folder → Dashboard → Chart (tile) → Topic → Semantic View → Physical Table

Prerequisites

Before running ingestion, ensure you have the following:

An Omni Organization API key with read access to models, documents, and connections. Generate API keys in Omni Admin → API Keys.
Connection mapping configuration if you want physical table lineage to stitch with existing warehouse entities in DataHub. You will need to map each Omni connection ID to the corresponding DataHub platform name, platform instance, and database name:

yaml

connection_to_platform:
  "conn_abc123": "snowflake"
connection_to_platform_instance:
  "conn_abc123": "my_snowflake_account"
connection_to_database:
  "conn_abc123": "ANALYTICS_PROD"

Connection IDs can be found by calling the Omni /v1/connections API or from the Omni Admin UI.

:::note If the Omni API key does not have permission to list connections (403 Forbidden), the connector will fall back to the connection_to_platform config overrides and continue ingestion without failing. :::