From 8960bd4d193a560dc5113f8e3d2d8a4acca4dcae Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 29 Jan 2025 11:33:59 +0000 Subject: [PATCH] Update column-level-lineage.md add enterprise lifecycle pill so it's easier to identify --- website/docs/docs/collaborate/column-level-lineage.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/docs/collaborate/column-level-lineage.md b/website/docs/docs/collaborate/column-level-lineage.md index 8c7116f2a18..3c149e7bdcf 100644 --- a/website/docs/docs/collaborate/column-level-lineage.md +++ b/website/docs/docs/collaborate/column-level-lineage.md @@ -3,6 +3,8 @@ title: "Column-level lineage" description: "Use dbt Explorer's column-level lineage to gain insights about your data at a granular level." --- +# Column-level lineage + dbt Explorer now offers column-level lineage (CLL) for the resources in your dbt project. Analytics engineers can quickly and easily gain insight into the provenance of their data products at a more granular level. For each column in a resource (model, source, or snapshot) in a dbt project, Explorer provides end-to-end lineage for the data in that column given how it's used. CLL is available to dbt Cloud Enterprise accounts that can use Explorer.