From 062fbc522ac5c80a617e4f4d36fa9bf230e6f065 Mon Sep 17 00:00:00 2001 From: Cameron Afzal Date: Tue, 13 Feb 2024 14:09:50 -0800 Subject: [PATCH] Reword CLL prereqs for clarity --- website/docs/docs/collaborate/column-level-lineage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/collaborate/column-level-lineage.md b/website/docs/docs/collaborate/column-level-lineage.md index 6ca3d033bbc..ea340aeb728 100644 --- a/website/docs/docs/collaborate/column-level-lineage.md +++ b/website/docs/docs/collaborate/column-level-lineage.md @@ -17,7 +17,7 @@ Explorer's CLL is currently available as a [public beta](/docs/dbt-versions/prod There is no additional setup required for CLL if your account is on an Enterprise plan that can use Explorer. You can access the CLL by expanding the column card in the **Columns** tab of an Explorer [resource details page](/docs/collaborate/explore-projects#view-resource-details) for a model, source, or snapshot. -dbt updates the lineage after each run that's executed in the production environment. You must make sure that `dbt docs generate` runs within at least one job in the environment. Refer to [Generating metadata](/docs/collaborate/explore-projects#generate-metadata) for more details. +dbt Cloud updates the lineage in Explorer after each run that's executed in the production environment. At least one job in the production environment must run `dbt docs generate`. Refer to [Generating metadata](/docs/collaborate/explore-projects#generate-metadata) for more details. @@ -53,4 +53,4 @@ Possible error cases are: - **Parsing error** — Error occurs when the SQL is ambiguous or too complex for parsing. An example of ambiguous parsing scenarios are _complex_ lateral joins. - **Python error** — Error occurs when a Python model is used within the lineage. Due to the nature of Python models, it's not possible to parse and determine the lineage. -- **Unknown error** — Error occurs when the lineage can't be determined for an unknown reason. An example of this would be if a dbt best practice is not being followed, like using hardcoded table names instead of `ref` statements. \ No newline at end of file +- **Unknown error** — Error occurs when the lineage can't be determined for an unknown reason. An example of this would be if a dbt best practice is not being followed, like using hardcoded table names instead of `ref` statements.