Skip to Content
šŸš€ We are currently in Private Beta. Check it out!
TroubleshootingMissing column lineage

Missing column lineage

Colibri relies on compiled SQL to determine column-level lineage. If you are missing column lineage, it might be for the entire project or just specific columns.

All column lineage is missing

If you only see table-to-table lineage, it usually means dbt compile has not been run.

Ensure that you have completely compiled manifest.json and catalog.json. Depending on your setup you might have to point to your prod target.

dbt compile --target {your_target} dbt docs generate --target {your_target}

After compiling, regenerate your Colibri artifacts and column-level lineage should appear.

Lineage is missing for specific columns

If most of your lineage is intact but specific columns are missing, it can happen for several reasons:

  • Column has no SQL logic Example: current_timestamp() as updated_at. Colibri will not trace lineage for columns that are simple expressions with no upstream references.

  • No catalog record for the column Ensure that the parent table of the column is materialized in production. Colibri needs catalog information to track column-level lineage.

  • Else: Run Colibri in debug mode to pinpoint the issue:

    colibri generate --debug

    If the issue persists, please raise a bug reportĀ .

Last updated on