Column lineage

Embrasure combines column mappings from these evidence paths:

SQL parsing for supported warehouse query history.
Warehouse-native lineage from Snowflake and Databricks.
The OpenLineage columnLineage facet from runtime producers.
Column fields from Google Data Lineage and other cloud feeds.
Compiled SQL and declarations from dbt and SQLMesh artifacts.
Enabled mappings from ingestion and CDC systems such as Fivetran and Debezium.
Semantic-model expressions from supported BI systems.
Lower-authority static repository enrichment.

Read precision

State	Action
`resolved`	Use the mapping for direct column impact.
`partial`	Inspect unresolved inputs and outputs.
`star`	Replace wildcards when exact expansion matters.
`unparseable`	Check the SQL dialect or provider payload.
`truncated`	Narrow the request or page through the remainder.

Scope impact by repeating column_ref:

curl --get https://api.embrasure.ai/v1/lineage/impact \
  --header "Authorization: Bearer $EMBRASURE_API_TOKEN" \
  --data-urlencode "workspace_id=$WORKSPACE_ID" \
  --data-urlencode "connector_id=$CONNECTOR_ID" \
  --data-urlencode "relation_ref=catalog.schema.orders" \
  --data-urlencode "column_ref=customer_id" \
  --data-urlencode "column_ref=total_amount" \
  --data-urlencode "direction=downstream"

Static repository enrichment

Configure enrichment on a linked GitHub project:

{
  "repositories": ["company/data-platform"],
  "branches": ["main"],
  "include_paths": ["models/**"],
  "exclude_paths": ["target/**"],
  "environment_map": {"main": "production"}
}

The analyzer records repository, commit SHA, source path, line location, parsed expression, and confidence. Static edges remain lower-authority evidence and cannot override conflicting runtime or warehouse-native mappings.

Change review reports exact column impact only when the graph has confirmed column evidence. Table-only evidence stays labeled at table precision.

Read precision

Static repository enrichment

On this page