Skip to main content

Lineage Troubleshooting

Source Query and Upstream Lineage Not Visible​

Lineage is computed based on the last 30 days. Has the asset been refreshed during this period?

Source Query Visible but No Upstream Lineage​

Are Both Parent and Children in Catalog? Is the Source of the Table in Catalog?​

Catalog computes lineage between assets that are available in Catalog. Does Catalog have sufficient rights to extract missing metadata?

Are You Using Multiple Layers of Temporary Tables To Create Your Asset?​

Catalog supports 2 levels of temporary tables by default. If you use more, reach out to your Catalog point of contact and we will increase the setting.

Source Query Visible but Truncated​

Catalog supports full visualization of queries that have up to 100,000 characters. When a query passes this limit, it is displayed with << TRUNCATED >> and only table-level upstream lineage is calculated.

Source Query of Temporary Table Shown for Materialized Table​

To match a source query with its associated table, Catalog uses the path of the asset. If you have a temporary table with the exact same name and path as a materialized one, there will be a conflict.

We suggest renaming the temporary table to a unique name.

Looker Specific​

Cannot See Lineage for Looker Assets​

Catalog computes lineage by analyzing your LookML. Have you provided access to your LookML repo to Catalog? See the Looker LookML access documentation for more information.

Some Looker Assets Do Not Have Lineage​

Catalog consistently improves the lineage engine with new scenarios. Here is a non-exhaustive list of scenarios not yet covered (coming soon):

  • {view_name.SQL_TABLE_NAME} pattern
  • Hidden fields used in calculated fields
  • Conditional lineage: Liquid
  • Native derived table
  • Refined explores

Still Facing Lineage Issues?​

Do not hesitate to reach out to your Catalog point of contact with your case. We will be happy to help investigate the missing links.