Omni Post

Capabilities

Use the Important Capabilities table above as the source of truth for supported features and whether additional configuration is required.

Physical table lineage

Omni Views reference physical warehouse tables via sql_table_name in model YAML. The connector resolves each reference to a DataHub dataset URN using the connection_to_platform mapping. If normalize_snowflake_names: true (default), database, schema, and table name components are uppercased to match the casing used by the DataHub Snowflake connector.

Column-level lineage

When include_column_lineage: true (default), the connector emits FineGrainedLineage entries by parsing sql expressions in model YAML and matching field references to known view columns. This enables precise field-level impact analysis across the full chain:

physical_table.column → semantic_view.field → dashboard_tile.field

Schema metadata

For each Omni Semantic View, the connector emits a SchemaMetadata aspect containing one SchemaField per dimension and measure defined in model YAML:

• Dimensions: emitted with inferred native type (string, date, timestamp, number, boolean)
• Measures: emitted with aggregation type and native type NUMBER
• Field descriptions are extracted from the YAML description attribute when present

Model and document filtering

Use model_pattern and document_pattern to restrict ingestion to specific models or dashboards:

model_pattern:
  allow:
    - "^prod-.*"
  deny:
    - ".*-dev$"

document_pattern:
  allow:
    - ".*"

Limitations

• Access Filters, User Attributes, and Cache schedules are not yet ingested.
• Column lineage is limited to fields that appear in model YAML sql expressions; complex or fully derived expressions may not fully resolve.
• Large organizations with many models may approach Omni API rate limits; tune max_requests_per_minute accordingly.
• True end-to-end integration tests require a live Omni environment; the test suite uses deterministic mock API responses.

Troubleshooting

If ingestion fails, validate credentials, permissions, and connectivity first. Then review the ingestion report and logs for source-specific errors.

Common issues: