From 0dd1d2863907a7e847d11a14e9c28d72608a4beb Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 12:43:08 +0000 Subject: [PATCH 01/23] add callout for deprecation --- website/docs/docs/build/metrics.md | 14 +++----------- .../avail-sl-integrations.md | 4 ++-- website/docs/docs/use-dbt-semantic-layer/dbt-sl.md | 4 ++-- .../docs/use-dbt-semantic-layer/quickstart-sl.md | 4 ++-- .../docs/docs/use-dbt-semantic-layer/setup-sl.md | 4 ++-- .../docs/use-dbt-semantic-layer/sl-architecture.md | 4 ++++ website/snippets/sl-deprecation-notice.md | 8 ++++++++ 7 files changed, 23 insertions(+), 19 deletions(-) create mode 100644 website/snippets/sl-deprecation-notice.md diff --git a/website/docs/docs/build/metrics.md b/website/docs/docs/build/metrics.md index 7a505fdad14..6d4e0fec893 100644 --- a/website/docs/docs/build/metrics.md +++ b/website/docs/docs/build/metrics.md @@ -7,13 +7,9 @@ keywords: tags: [Metrics] --- -:::caution Upgrade to access MetricFlow and the new dbt Semantic Layer +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; -The dbt_metrics package has been deprecated and replaced with [MetricFlow](/docs/build/about-metricflow?version=1.6). If you're using the dbt_metrics package or the legacy Semantic Layer (available on v1.5 or lower), we **highly** recommend [upgrading your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to access MetricFlow and the new [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl?version=1.6). - -To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/migration/sl-migration) for more info. - -::: + @@ -38,11 +34,7 @@ A metric is an aggregation over a that supports zero or more - active users - monthly recurring revenue (mrr) -In v1.0, dbt supports metric definitions as a new node type. Like [exposures](exposures), metrics appear as nodes in the directed acyclic graph (DAG) and can be expressed in YAML files. Defining metrics in dbt projects encodes crucial business logic in tested, version-controlled code. Further, you can expose these metrics definitions to downstream tooling, which drives consistency and precision in metric reporting. - -Review the video below to learn more about metrics, why they're important, and how to get started: - - +In v1.0, dbt supports metric definitions as a new node type. Like [exposures](exposures), metrics appear as nodes in the directed acyclic graph (DAG) and can be expressed in YAML files. Defining metrics in dbt projects encodes crucial business logic in tested, version-controlled code. Further, you can expose these metrics definitions to downstream tooling, which drives consistency and precision in metric reporting. ### Benefits of defining metrics diff --git a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md index 22178a14b5b..4f009db1819 100644 --- a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md +++ b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md @@ -38,9 +38,9 @@ import AvailIntegrations from '/snippets/_sl-partner-links.md'; -import LegacyInfo from '/snippets/_legacy-sl-callout.md'; +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; - + A wide variety of data applications across the modern data stack natively integrate with the dbt Semantic Layer and dbt metrics — from Business Intelligence tools to notebooks, data catalogs, and more. diff --git a/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md b/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md index 8c78d556a67..b1a2c2ecaa9 100644 --- a/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md @@ -67,9 +67,9 @@ plan="dbt Cloud Team or Enterprise" -import LegacyInfo from '/snippets/_legacy-sl-callout.md'; +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; - + The dbt Semantic Layer allows your data teams to centrally define essential business metrics like `revenue`, `customer`, and `churn` in the modeling layer (your dbt project) for consistent self-service within downstream data tools like BI and metadata management solutions. The dbt Semantic Layer provides the flexibility to define metrics on top of your existing models and then query those metrics and models in your analysis tools of choice. diff --git a/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md b/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md index 42f08a90401..f68b0e144d1 100644 --- a/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md @@ -114,9 +114,9 @@ User data passes through the Semantic Layer on its way back from the warehouse. -import LegacyInfo from '/snippets/_legacy-sl-callout.md'; +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; - + To try out the features of the dbt Semantic Layer, you first need to have a dbt project set up. This quickstart guide will lay out the following steps, and recommends a workflow that demonstrates some of its essential features: diff --git a/website/docs/docs/use-dbt-semantic-layer/setup-sl.md b/website/docs/docs/use-dbt-semantic-layer/setup-sl.md index 4c88ee50b25..6fc7a018b8b 100644 --- a/website/docs/docs/use-dbt-semantic-layer/setup-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/setup-sl.md @@ -39,9 +39,9 @@ import SlSetUp from '/snippets/_new-sl-setup.md'; -import LegacyInfo from '/snippets/_legacy-sl-callout.md'; +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; - + With the dbt Semantic Layer, you can define business metrics, reduce code duplication and inconsistency, create self-service in downstream tools, and more. Configure the dbt Semantic Layer in dbt Cloud to connect with your integrated partner tool. diff --git a/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md b/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md index 9e8737c68d3..a1a19ead040 100644 --- a/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md +++ b/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md @@ -56,6 +56,10 @@ The dbt Semantic Layer is proprietary; however, some components of the dbt Seman +import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; + + + ## Product architecture The dbt Semantic Layer product architecture includes four primary components: diff --git a/website/snippets/sl-deprecation-notice.md b/website/snippets/sl-deprecation-notice.md new file mode 100644 index 00000000000..ec49fd28fbf --- /dev/null +++ b/website/snippets/sl-deprecation-notice.md @@ -0,0 +1,8 @@ +:::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer +If you're reading this message, you're either using an older version of our documentation or currently use the legacy Semantic Layer. + +As of December 15th, 2023, dbt Metrics and the legacy dbt Semantic Layer (v1.5 and lower) will no longer be supported. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. + +After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. + +::: From 6c5ab74eca9b6c13401b5b0328f11aa9f7ef62e9 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 12:50:41 +0000 Subject: [PATCH 02/23] adding bullets for consistency --- website/docs/docs/use-dbt-semantic-layer/gsheets.md | 8 ++++---- website/docs/docs/use-dbt-semantic-layer/tableau.md | 9 +++++---- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/gsheets.md b/website/docs/docs/use-dbt-semantic-layer/gsheets.md index ee391c91b70..2bbba70f98e 100644 --- a/website/docs/docs/use-dbt-semantic-layer/gsheets.md +++ b/website/docs/docs/use-dbt-semantic-layer/gsheets.md @@ -13,10 +13,10 @@ The dbt Semantic Layer offers a seamless integration with Google Sheets through ## Prerequisites -1. You have a Google account with access to Google Sheets. -2. You can install Google add-ons. -3. You have [set up the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl). -4. You have a dbt Cloud Environment ID and a [service token](/docs/dbt-cloud-apis/service-tokens) to authenticate with from a dbt Cloud account. +- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using the latest version. +- You have a Google account with access to Google Sheets. +- You can install Google add-ons. +- You have a dbt Cloud Environment ID and a [service token](/docs/dbt-cloud-apis/service-tokens) to authenticate with from a dbt Cloud account. ## Installing the add-on diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index c93643354aa..fe02b33d89d 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -16,11 +16,12 @@ This integration provides a live connection to the dbt Semantic Layer through Ta ## Prerequisites -1. You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed with version 2021.1 or greater +- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using the latest version. +- You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed with version 2021.1 or greater - Note that Tableau Online does not currently support custom connectors natively. -2. Log in to Tableau Desktop using either your license or the login details you use for Tableau Server or Tableau Online. -3. You need your dbt Cloud host, [Environment ID](/docs/use-dbt-semantic-layer/setup-sl#set-up-dbt-semantic-layer) and [service token](/docs/dbt-cloud-apis/service-tokens) to log in. This account should be set up with the dbt Semantic Layer. -4. You must have a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) +- Log in to Tableau Desktop using either your license or the login details you use for Tableau Server or Tableau Online. +- You need your dbt Cloud host, [Environment ID](/docs/use-dbt-semantic-layer/setup-sl#set-up-dbt-semantic-layer) and [service token](/docs/dbt-cloud-apis/service-tokens) to log in. This account should be set up with the dbt Semantic Layer. +- You must have a dbt Cloud Team or Enterprise [account](https://www.getdbt.com/pricing) and multi-tenant [deployment](/docs/cloud/about-cloud/regions-ip-addresses). (Single-Tenant coming soon) ## Installing From d106cb5aaac4c5320c7df6afda44f8cf7dd37bb1 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 12:59:22 +0000 Subject: [PATCH 03/23] update api callout --- website/snippets/_legacy-sl-callout.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/snippets/_legacy-sl-callout.md b/website/snippets/_legacy-sl-callout.md index f45c6b68af3..1f1de95ce17 100644 --- a/website/snippets/_legacy-sl-callout.md +++ b/website/snippets/_legacy-sl-callout.md @@ -1,11 +1,11 @@ -:::important Upgrade to access the new dbt Semantic Layer +:::important Upgrade to access the latest dbt Semantic Layer -The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), improving governance, introducing a new API, and making it more efficient to define and query metrics. The legacy Semantic Layer, available in dbt v1.5 or lower, is no longer supported and won't receive any code fixes. +The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), introducing new features such as dbt Semantic Layer APIs. The APIs integrate with data applications, such as Tableau and Google Sheets, to query metrics and unlock insights. -**Who does this affect?** Anyone who uses the legacy Semantic Layer. The new Semantic Layer is available to [Team or Enterprise](https://www.getdbt.com/pricing/) multi-tenant dbt Cloud plans [hosted in North America](/docs/cloud/about-cloud/regions-ip-addresses) (more regions coming soon). You must be on dbt v1.6 or higher to access it. Users on dbt Cloud Developer plans or dbt Core users can use MetricFlow to only define and test metrics locally. +If you're reading this message, you're either using an older version of our documentation or currently use the legacy Semantic Layer. -**What’s changed?** The dbt_metrics package has been [deprecated](https://docs.getdbt.com/blog/deprecating-dbt-metrics) and replaced with [MetricFlow](/docs/build/about-metricflow?version=1.6), a new framework for defining metrics in dbt. This means dbt_metrics is no longer supported after dbt v1.5 and won't receive any code fixes. +As of December 15th, 2023, dbt Metrics and the legacy dbt Semantic Layer (v1.5 and lower) will no longer be supported. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. -**What should you do?** If you're using the legacy Semantic Layer, we **highly** recommend you [upgrade your dbt version](/docs/dbt-versions/upgrade-core-in-cloud) to dbt v1.6 or higher to use the new dbt Semantic Layer. To migrate to the new Semantic Layer, refer to the dedicated [migration guide](/guides/migration/sl-migration) for more info. +After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. ::: From e48c8214ba0b2d613470a956eb5118dbf06d08d7 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 16:14:44 +0000 Subject: [PATCH 04/23] update --- .../docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md | 2 +- website/docs/docs/use-dbt-semantic-layer/dbt-sl.md | 2 +- website/docs/docs/use-dbt-semantic-layer/gsheets.md | 2 +- website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md | 2 +- website/docs/docs/use-dbt-semantic-layer/setup-sl.md | 2 +- website/docs/docs/use-dbt-semantic-layer/sl-architecture.md | 2 +- website/docs/docs/use-dbt-semantic-layer/tableau.md | 2 +- .../{sl-deprecation-notice.md => _sl-deprecation-notice.md} | 0 8 files changed, 7 insertions(+), 7 deletions(-) rename website/snippets/{sl-deprecation-notice.md => _sl-deprecation-notice.md} (100%) diff --git a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md index 4f009db1819..4f4621fa860 100644 --- a/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md +++ b/website/docs/docs/use-dbt-semantic-layer/avail-sl-integrations.md @@ -38,7 +38,7 @@ import AvailIntegrations from '/snippets/_sl-partner-links.md'; -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; diff --git a/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md b/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md index b1a2c2ecaa9..9c9933340bd 100644 --- a/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/dbt-sl.md @@ -67,7 +67,7 @@ plan="dbt Cloud Team or Enterprise" -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; diff --git a/website/docs/docs/use-dbt-semantic-layer/gsheets.md b/website/docs/docs/use-dbt-semantic-layer/gsheets.md index 2bbba70f98e..cb9f4014803 100644 --- a/website/docs/docs/use-dbt-semantic-layer/gsheets.md +++ b/website/docs/docs/use-dbt-semantic-layer/gsheets.md @@ -13,7 +13,7 @@ The dbt Semantic Layer offers a seamless integration with Google Sheets through ## Prerequisites -- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using the latest version. +- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using dbt v1.6 or higher. - You have a Google account with access to Google Sheets. - You can install Google add-ons. - You have a dbt Cloud Environment ID and a [service token](/docs/dbt-cloud-apis/service-tokens) to authenticate with from a dbt Cloud account. diff --git a/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md b/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md index f68b0e144d1..7e77c075ce6 100644 --- a/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/quickstart-sl.md @@ -114,7 +114,7 @@ User data passes through the Semantic Layer on its way back from the warehouse. -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; diff --git a/website/docs/docs/use-dbt-semantic-layer/setup-sl.md b/website/docs/docs/use-dbt-semantic-layer/setup-sl.md index 6fc7a018b8b..9997e2d3647 100644 --- a/website/docs/docs/use-dbt-semantic-layer/setup-sl.md +++ b/website/docs/docs/use-dbt-semantic-layer/setup-sl.md @@ -39,7 +39,7 @@ import SlSetUp from '/snippets/_new-sl-setup.md'; -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; diff --git a/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md b/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md index a1a19ead040..a44144f61d6 100644 --- a/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md +++ b/website/docs/docs/use-dbt-semantic-layer/sl-architecture.md @@ -56,7 +56,7 @@ The dbt Semantic Layer is proprietary; however, some components of the dbt Seman -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; diff --git a/website/docs/docs/use-dbt-semantic-layer/tableau.md b/website/docs/docs/use-dbt-semantic-layer/tableau.md index fe02b33d89d..8e6d7d8ed27 100644 --- a/website/docs/docs/use-dbt-semantic-layer/tableau.md +++ b/website/docs/docs/use-dbt-semantic-layer/tableau.md @@ -16,7 +16,7 @@ This integration provides a live connection to the dbt Semantic Layer through Ta ## Prerequisites -- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using the latest version. +- You have [configured the dbt Semantic Layer](/docs/use-dbt-semantic-layer/setup-sl) and are using dbt v1.6 or higher. - You must have [Tableau Desktop](https://www.tableau.com/en-gb/products/desktop) installed with version 2021.1 or greater - Note that Tableau Online does not currently support custom connectors natively. - Log in to Tableau Desktop using either your license or the login details you use for Tableau Server or Tableau Online. diff --git a/website/snippets/sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md similarity index 100% rename from website/snippets/sl-deprecation-notice.md rename to website/snippets/_sl-deprecation-notice.md From 9148b87836832f821434724bca77eb570153c3fa Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 16:21:34 +0000 Subject: [PATCH 05/23] fix snippet --- website/docs/docs/build/metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/build/metrics.md b/website/docs/docs/build/metrics.md index 6d4e0fec893..6686dadc356 100644 --- a/website/docs/docs/build/metrics.md +++ b/website/docs/docs/build/metrics.md @@ -7,7 +7,7 @@ keywords: tags: [Metrics] --- -import DeprecationNotice from '/snippets/sl-deprecation-notice.md'; +import DeprecationNotice from '/snippets/_sl-deprecation-notice.md'; From cfab9a4eb5e766ad672c3c5620d10da771da2a32 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 16:55:55 +0000 Subject: [PATCH 06/23] will's feedback --- website/snippets/_legacy-sl-callout.md | 7 +++---- website/snippets/_sl-deprecation-notice.md | 4 +--- 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/website/snippets/_legacy-sl-callout.md b/website/snippets/_legacy-sl-callout.md index 1f1de95ce17..61d3a1c910f 100644 --- a/website/snippets/_legacy-sl-callout.md +++ b/website/snippets/_legacy-sl-callout.md @@ -1,11 +1,10 @@ :::important Upgrade to access the latest dbt Semantic Layer -The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), introducing new features such as dbt Semantic Layer APIs. The APIs integrate with data applications, such as Tableau and Google Sheets, to query metrics and unlock insights. +The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), introducing new features such as dbt Semantic Layer APIs. The APIs integrate with data applications, such as Tableau and Google Sheets, to query metrics and unlock insights. -If you're reading this message, you're either using an older version of our documentation or currently use the legacy Semantic Layer. - -As of December 15th, 2023, dbt Metrics and the legacy dbt Semantic Layer (v1.5 and lower) will no longer be supported. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. +For users on dbt version 1.5 or earlier, starting on December 15th, 2023, support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. ::: +support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index ec49fd28fbf..8d107f39fff 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,7 +1,5 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer -If you're reading this message, you're either using an older version of our documentation or currently use the legacy Semantic Layer. - -As of December 15th, 2023, dbt Metrics and the legacy dbt Semantic Layer (v1.5 and lower) will no longer be supported. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. +For users on dbt version 1.5 or earlier — starting on December 15th, 2023, support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. From 875f6eb1a14854dda9977cac6f152ca70fbfbe51 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Fri, 10 Nov 2023 10:51:10 +0000 Subject: [PATCH 07/23] clarify dbt rules for defer --- .../docs/docs/cloud/about-cloud-develop-defer.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 95e745fe963..48c4388578c 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -7,9 +7,20 @@ pagination_next: "docs/cloud/cloud-cli-installation" --- -[Defer](/reference/node-selection/defer) is a powerful feature that allows developers to only build and run and test models they've edited without having to first run and build all the models that come before them (upstream parents). This is powered by using a production manifest for comparison, and dbt will resolve the `{{ ref() }}` function with upstream production artifacts. +[Defer](/reference/node-selection/defer) is a powerful feature that allows developers to only build and run and test models they've edited without having to first run and build all the models that come before them (upstream parents). This is powered by using a production manifest for comparison, and dbt will resolve the `{{ ref() }}` function with upstream production artifacts. -Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows, dramatically reducing development time and warehouse spend by preventing unnecessary model builds. +By default, dbt follows these rules: + +- Defers to the production environment when there's no development schema. +- If a development schema exists, dbt will prioritize those changes, which minimizes development time and avoids unnecessary model builds. + +Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows. + +For specific scenarios: +- Use [`--favor-state`](/reference/node-selection/defer#favor-state) to always use production artifacts to resolve the ref. +- If facing issues with outdated tables in the dev schema, `--favor-state` is an alternative to defer. + +For a clean slate, it's a good practice to drop the dev schema at the start and end of your development cycle. ## Required setup From 1da1108401184321e93f7614e4baf6019803eb66 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Fri, 10 Nov 2023 10:51:40 +0000 Subject: [PATCH 08/23] consistency --- website/docs/docs/cloud/about-cloud-develop-defer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 48c4388578c..1861a6d8a79 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -18,9 +18,9 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr For specific scenarios: - Use [`--favor-state`](/reference/node-selection/defer#favor-state) to always use production artifacts to resolve the ref. -- If facing issues with outdated tables in the dev schema, `--favor-state` is an alternative to defer. +- If facing issues with outdated tables in the development schema, `--favor-state` is an alternative to defer. -For a clean slate, it's a good practice to drop the dev schema at the start and end of your development cycle. +For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle. ## Required setup From e0e8309bc879fdc7202f69b25430aa0e19e832e1 Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 13:35:10 -0700 Subject: [PATCH 09/23] Update page title --- website/docs/reference/source-properties.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/website/docs/reference/source-properties.md b/website/docs/reference/source-properties.md index d20ef5f2877..d107881967e 100644 --- a/website/docs/reference/source-properties.md +++ b/website/docs/reference/source-properties.md @@ -1,5 +1,5 @@ --- -title: "About source properties" +title: "Source properties" description: "Learn how to use source properties in dbt." --- @@ -8,9 +8,13 @@ description: "Learn how to use source properties in dbt." - [Declaring resource properties](/reference/configs-and-properties) ## Overview -Source properties can be declared in `.yml` files in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)). -You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory. +import PropsCallout from '/snippets/_config-prop-callout.md'; + +Source properties can be declared in any `properties.yml` file in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)).
+ + +You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory: From 26d7cf1fbb3e1b642b5f62264c35527d0cc62dd6 Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 14:02:52 -0700 Subject: [PATCH 10/23] Small whitespace and verbiage changes --- website/docs/reference/configs-and-properties.md | 5 ++++- website/docs/reference/dbt_project.yml.md | 3 ++- website/docs/reference/resource-configs/docs.md | 10 ++-------- 3 files changed, 8 insertions(+), 10 deletions(-) diff --git a/website/docs/reference/configs-and-properties.md b/website/docs/reference/configs-and-properties.md index c2ad5b77629..75c8e1594b1 100644 --- a/website/docs/reference/configs-and-properties.md +++ b/website/docs/reference/configs-and-properties.md @@ -11,7 +11,7 @@ A rule of thumb: properties declare things _about_ your project resources; confi For example, you can use resource **properties** to: * Describe models, snapshots, seed files, and their columns -- Assert "truths" about a model, in the form of [tests](/docs/build/tests), e.g. "this `id` column is unique" +* Assert "truths" about a model, in the form of [tests](/docs/build/tests), e.g. "this `id` column is unique" * Define pointers to existing tables that contain raw data, in the form of [sources](/docs/build/sources), and assert the expected "freshness" of this raw data * Define official downstream uses of your data models, in the form of [exposures](/docs/build/exposures) @@ -67,12 +67,14 @@ Previous versions of the docs referred to these as `schema.yml` files — we've dbt has the ability to define node configs in `.yml` files, in addition to `config()` blocks and `dbt_project.yml`. But the reverse isn't always true: there are some things in `.yml` files that can _only_ be defined there. Certain properties are special, because: + - They have a unique Jinja rendering context - They create new project resources - They don't make sense as hierarchical configuration - They're older properties that haven't yet been redefined as configs These properties are: + - [`description`](/reference/resource-properties/description) - [`tests`](/reference/resource-properties/tests) - [`docs`](/reference/resource-configs/docs) @@ -202,3 +204,4 @@ Runtime Error ``` This error occurred because a semicolon (`;`) was accidentally used instead of a colon (`:`) after the `description` field. To resolve issues like this, find the `.yml` file referenced in the error message and fix any syntax errors present in the file. There are online YAML validators that can be helpful here, but please be mindful of submitting sensitive information to third-party applications! + diff --git a/website/docs/reference/dbt_project.yml.md b/website/docs/reference/dbt_project.yml.md index 9bd85d0d5dd..caf501c27ab 100644 --- a/website/docs/reference/dbt_project.yml.md +++ b/website/docs/reference/dbt_project.yml.md @@ -1,5 +1,5 @@ -Every [dbt project](/docs/build/projects) needs a `dbt_project.yml` file — this is how dbt knows a directory is a dbt project. It also contains important information that tells dbt how to operate on your project. +Every [dbt project](/docs/build/projects) needs a `dbt_project.yml` file — this is how dbt knows a directory is a dbt project. It also contains important information that tells dbt how to operate your project. @@ -96,6 +96,7 @@ vars: + ```yml diff --git a/website/docs/reference/resource-configs/docs.md b/website/docs/reference/resource-configs/docs.md index 0ccd21d7504..d300979a826 100644 --- a/website/docs/reference/resource-configs/docs.md +++ b/website/docs/reference/resource-configs/docs.md @@ -17,10 +17,12 @@ default_value: {show: true} { label: 'Macros', value: 'macros', }, ] }> + + ```yml version: 2 @@ -29,7 +31,6 @@ models: docs: show: true | false node_color: "black" - ``` @@ -53,9 +54,7 @@ seeds: - name: seed_name docs: show: true | false - ``` - @@ -71,9 +70,7 @@ snapshots: - name: snapshot_name docs: show: true | false - ``` - @@ -90,7 +87,6 @@ analyses: docs: show: true | false ``` - @@ -110,9 +106,7 @@ macros: - name: macro_name docs: show: true | false - ``` - Also refer to [macro properties](/reference/macro-properties). From 5863a3d7978aa5b1745ae871541812cff5313f77 Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 14:14:05 -0700 Subject: [PATCH 11/23] Revert "Update page title" This reverts commit e0e8309bc879fdc7202f69b25430aa0e19e832e1. --- website/docs/reference/source-properties.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/website/docs/reference/source-properties.md b/website/docs/reference/source-properties.md index d107881967e..d20ef5f2877 100644 --- a/website/docs/reference/source-properties.md +++ b/website/docs/reference/source-properties.md @@ -1,5 +1,5 @@ --- -title: "Source properties" +title: "About source properties" description: "Learn how to use source properties in dbt." --- @@ -8,13 +8,9 @@ description: "Learn how to use source properties in dbt." - [Declaring resource properties](/reference/configs-and-properties) ## Overview +Source properties can be declared in `.yml` files in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)). -import PropsCallout from '/snippets/_config-prop-callout.md'; - -Source properties can be declared in any `properties.yml` file in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)).
- - -You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory: +You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory. From 6431a3a898537fb59127171456f15e8d431db786 Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 14:17:27 -0700 Subject: [PATCH 12/23] Update page title --- website/docs/reference/source-properties.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/source-properties.md b/website/docs/reference/source-properties.md index d20ef5f2877..1fc7a4aef55 100644 --- a/website/docs/reference/source-properties.md +++ b/website/docs/reference/source-properties.md @@ -1,5 +1,5 @@ --- -title: "About source properties" +title: "Source properties" description: "Learn how to use source properties in dbt." --- From 05e744905f411c94e6c9d9abb757cea1d7721c2a Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 14:40:14 -0700 Subject: [PATCH 13/23] Remove hyphenation --- website/docs/reference/configs-and-properties.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/reference/configs-and-properties.md b/website/docs/reference/configs-and-properties.md index 75c8e1594b1..8a557c762ed 100644 --- a/website/docs/reference/configs-and-properties.md +++ b/website/docs/reference/configs-and-properties.md @@ -35,11 +35,11 @@ dbt prioritizes configurations in order of specificity, from most specificity to Note - Generic tests work a little differently when it comes to specificity. See [test configs](/reference/test-configs). -Within the project file, configurations are also applied hierarchically. The most-specific config always "wins": In the project file, configurations applied to a `marketing` subdirectory will take precedence over configurations applied to the entire `jaffle_shop` project. To apply a configuration to a model, or directory of models, define the resource path as nested dictionary keys. +Within the project file, configurations are also applied hierarchically. The most specific config always "wins": In the project file, configurations applied to a `marketing` subdirectory will take precedence over configurations applied to the entire `jaffle_shop` project. To apply a configuration to a model, or directory of models, define the resource path as nested dictionary keys. ### Combining configs -Most configurations are "clobbered" when applied hierarchically. Whenever a more-specific value is available, it will completely replace the less-specific value. Note that a few configs have different merge behavior: +Most configurations are "clobbered" when applied hierarchically. Whenever a more specific value is available, it will completely replace the less specific value. Note that a few configs have different merge behavior: - [`tags`](tags) are additive. If a model has some tags configured in `dbt_project.yml`, and more tags applied in its `.sql` file, the final set of tags will include all of them. - [`meta`](/reference/resource-configs/meta) dictionaries are merged (a more specific key-value pair replaces a less specific value with the same key) - [`pre-hook` and `post-hook`](/reference/resource-configs/pre-hook-post-hook) are also additive. From dac137daca30774e38d46580da95479deb5108cd Mon Sep 17 00:00:00 2001 From: Doug Beatty Date: Fri, 10 Nov 2023 15:16:38 -0700 Subject: [PATCH 14/23] Callout snippet for properties and configs --- website/docs/reference/analysis-properties.md | 4 +++- website/docs/reference/exposure-properties.md | 6 +++++- website/docs/reference/macro-properties.md | 7 +++++-- website/docs/reference/source-properties.md | 8 ++++++-- website/snippets/_config-prop-callout.md | 1 + 5 files changed, 20 insertions(+), 6 deletions(-) create mode 100644 website/snippets/_config-prop-callout.md diff --git a/website/docs/reference/analysis-properties.md b/website/docs/reference/analysis-properties.md index fbc7b05538f..880aeddbb0d 100644 --- a/website/docs/reference/analysis-properties.md +++ b/website/docs/reference/analysis-properties.md @@ -2,7 +2,9 @@ title: Analysis properties --- -We recommend you define analysis properties in your `analyses/` directory, which is illustrated in the [`analysis-paths`](/reference/project-configs/analysis-paths) configuration. +import PropsCallout from '/snippets/_config-prop-callout.md'; + +We recommend you define analysis properties in your `analyses/` directory, which is illustrated in the [`analysis-paths`](/reference/project-configs/analysis-paths) configuration.
You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `analyses/` or `models/` directory. diff --git a/website/docs/reference/exposure-properties.md b/website/docs/reference/exposure-properties.md index aaed2a20a09..0bd4cf771af 100644 --- a/website/docs/reference/exposure-properties.md +++ b/website/docs/reference/exposure-properties.md @@ -8,7 +8,11 @@ description: "Read this guide to understand exposure properties in dbt." - [Declaring resource properties](/reference/configs-and-properties) ## Overview -Exposures are defined in `.yml` files nested under an `exposures:` key. You may define `exposures` in YAML files that also define define `sources` or `models`. + +import PropsCallout from '/snippets/_config-prop-callout.md'; + +Exposures are defined in `properties.yml` files nested under an `exposures:` key. You may define `exposures` in YAML files that also define `sources` or `models`.
+ You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory. diff --git a/website/docs/reference/macro-properties.md b/website/docs/reference/macro-properties.md index 9919835f3c5..91a616ded0d 100644 --- a/website/docs/reference/macro-properties.md +++ b/website/docs/reference/macro-properties.md @@ -1,10 +1,13 @@ --- title: Macro properties +id: macro-properties --- -Macro properties can be declared in `.yml` files. +import PropsCallout from '/snippets/_config-prop-callout.md'; -You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders. +Macro properties can be declared in any `properties.yml` file. + +You can name these files `whatever_you_want.yml` and nest them arbitrarily deep in sub-folders. diff --git a/website/docs/reference/source-properties.md b/website/docs/reference/source-properties.md index 1fc7a4aef55..d107881967e 100644 --- a/website/docs/reference/source-properties.md +++ b/website/docs/reference/source-properties.md @@ -8,9 +8,13 @@ description: "Learn how to use source properties in dbt." - [Declaring resource properties](/reference/configs-and-properties) ## Overview -Source properties can be declared in `.yml` files in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)). -You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory. +import PropsCallout from '/snippets/_config-prop-callout.md'; + +Source properties can be declared in any `properties.yml` file in your `models/` directory (as defined by the [`model-paths` config](/reference/project-configs/model-paths)).
+ + +You can name these files `whatever_you_want.yml`, and nest them arbitrarily deeply in subfolders within the `models/` directory: diff --git a/website/snippets/_config-prop-callout.md b/website/snippets/_config-prop-callout.md new file mode 100644 index 00000000000..f21c335734a --- /dev/null +++ b/website/snippets/_config-prop-callout.md @@ -0,0 +1 @@ +{props.title} are "special properties" in that you can't configure them in the dbt_project.yml file or using config() blocks. Refer to Configs and properties for more info. From cf000ccaa9d552e34ede9b2858d134f759d79b65 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 10:59:48 +0000 Subject: [PATCH 15/23] folding in williams' feedback --- .../semantic-layer-4-build-metrics.md | 2 +- website/docs/docs/build/metricflow-commands.md | 12 +++++++----- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics.md b/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics.md index 8b112f2f828..da83adbdc69 100644 --- a/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics.md +++ b/website/docs/best-practices/how-we-build-our-metrics/semantic-layer-4-build-metrics.md @@ -36,7 +36,7 @@ metrics: Use [MetricFlow commands](/docs/build/metricflow-commands#metricflow) for metric validation or queries during development, and apply the following conventions based on your environment: -- For dbt Cloud, use the `dbt sl` prefix before the command (such as, `dbt sl parse` or `dbt sl query`). +- For dbt Cloud, use the `dbt sl` prefix before the command (such as, `dbt sl query`). - For dbt Core, use the `mf` prefix (such as `mf validate-configs` or `mf query)`. Follow these best practices when updating your semantic layer code, using the `mf` command as an example (replace `mf` with `dbt sl` if you're using dbt Cloud): diff --git a/website/docs/docs/build/metricflow-commands.md b/website/docs/docs/build/metricflow-commands.md index fd120591900..4d2477ad2ed 100644 --- a/website/docs/docs/build/metricflow-commands.md +++ b/website/docs/docs/build/metricflow-commands.md @@ -179,8 +179,9 @@ Options: ### Validate-configs -This command performs validations against the defined semantic model configurations: - +The following command performs validations against the defined semantic model configurations. + +Note, in dbt Cloud you don't need to validate the Semantic Layer config separately. Running a dbt command (such as `dbt parse`, `dbt build`, `dbt compile`, `dbt run`) automatically checks it. ```bash @@ -205,11 +206,12 @@ Options: ### Health checks -This command performs a health check against the data platform you provided in the configs: - +The following command performs a health check against the data platform you provided in the configs. + +Note, in dbt Cloud the `health-checks` command isn't required since it uses dbt Cloud's credentials to perform the health check. ```bash -mf health-checks #in dbt Core +mf health-checks # In dbt Core ``` ### Tutorial From 437f78faa2351005bc94256ecc948fcc39ca37b9 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 11:02:11 +0000 Subject: [PATCH 16/23] Update website/snippets/_sl-deprecation-notice.md Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> --- website/snippets/_sl-deprecation-notice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index 8d107f39fff..07b672c1929 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,6 +1,6 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer For users on dbt version 1.5 or earlier — starting on December 15th, 2023, support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. -After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. +After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. ::: From e106c524c36ee3188070bb92d0e8ae0a0b734a53 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 11:12:53 +0000 Subject: [PATCH 17/23] clarify language --- website/snippets/_sl-deprecation-notice.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index 07b672c1929..95a7c7e26c7 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,5 +1,6 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer -For users on dbt version 1.5 or earlier — starting on December 15th, 2023, support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. +For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access enhanced features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/migration/sl-migration). + After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. From 4062f9e1e3175eca691b467beb988fde1443db61 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 11:13:13 +0000 Subject: [PATCH 18/23] use latest --- website/snippets/_sl-deprecation-notice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index 95a7c7e26c7..0e07f315976 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,5 +1,5 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer -For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access enhanced features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/migration/sl-migration). +For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/migration/sl-migration). After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. From 0e9bd1518cc99a41f8a50b4dd87223177842a070 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 11:15:40 +0000 Subject: [PATCH 19/23] fix link --- website/snippets/_sl-deprecation-notice.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index 0e07f315976..f521fedc7b4 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,5 +1,5 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer -For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/migration/sl-migration). +For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. From a36c3e71a56210159931fbf432aa68172a5dedcb Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 11:16:19 +0000 Subject: [PATCH 20/23] fix link --- website/snippets/_legacy-sl-callout.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/snippets/_legacy-sl-callout.md b/website/snippets/_legacy-sl-callout.md index 61d3a1c910f..ae40151ab1c 100644 --- a/website/snippets/_legacy-sl-callout.md +++ b/website/snippets/_legacy-sl-callout.md @@ -2,9 +2,8 @@ The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), introducing new features such as dbt Semantic Layer APIs. The APIs integrate with data applications, such as Tableau and Google Sheets, to query metrics and unlock insights. -For users on dbt version 1.5 or earlier, starting on December 15th, 2023, support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. To benefit from the latest features, upgrade to the most [recent version](/guides/migration/sl-migration) of dbt and embrace the enhanced dbt Semantic Layer, powered by MetricFlow. +For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). -After this date, dbt Labs won't offer support, bug fixes, or security updates for these deprecated features. Documentation for them will be discontinued, and they will be removed from the dbt Cloud user interface. +After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. ::: -support for dbt Metrics and the old dbt Semantic Layer (v1.5 and below) will end. From 882d19bbf68d9cc992a139a02feecb40c726a5dd Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 11:17:21 +0000 Subject: [PATCH 21/23] consistency --- website/snippets/_legacy-sl-callout.md | 2 +- website/snippets/_sl-deprecation-notice.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/website/snippets/_legacy-sl-callout.md b/website/snippets/_legacy-sl-callout.md index ae40151ab1c..b0575b60729 100644 --- a/website/snippets/_legacy-sl-callout.md +++ b/website/snippets/_legacy-sl-callout.md @@ -2,7 +2,7 @@ The dbt Semantic Layer has undergone a [significant revamp](https://www.getdbt.com/blog/dbt-semantic-layer-whats-next/), introducing new features such as dbt Semantic Layer APIs. The APIs integrate with data applications, such as Tableau and Google Sheets, to query metrics and unlock insights. -For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). +For users of the dbt Semantic Layer on version 1.5 or lower — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. diff --git a/website/snippets/_sl-deprecation-notice.md b/website/snippets/_sl-deprecation-notice.md index f521fedc7b4..19bf19c2d90 100644 --- a/website/snippets/_sl-deprecation-notice.md +++ b/website/snippets/_sl-deprecation-notice.md @@ -1,5 +1,5 @@ :::info Deprecation of dbt Metrics and the legacy dbt Semantic Layer -For users of the dbt Semantic Layer on version 1.5 or earlier — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). +For users of the dbt Semantic Layer on version 1.5 or lower — Support for dbt Metrics and the legacy dbt Semantic Layer ends on December 15th, 2023. To access the latest features, migrate to the updated version using the [dbt Semantic Layer migration guide](/guides/sl-migration). After December 15th, dbt Labs will no longer support these deprecated features, they will be removed from the dbt Cloud user interface, and their documentation removed from the docs site. From 08cd63b4675e2c44ca329e6d8062e6b30fde4c28 Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Mon, 13 Nov 2023 09:55:43 -0700 Subject: [PATCH 22/23] Fix rendering of hyperlink (#4450) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ### Preview - Click on the "macros" tab: - https://docs-getdbt-com-git-dbeatty-docs-config-fix-link-dbt-labs.vercel.app/reference/resource-configs/docs ## What are you changing in this pull request and why? This hyperlink isn't rendering correctly: image ### 🎩 Preview after the fix: image ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [x] I have checked the preview renders correctly --- website/docs/reference/resource-configs/docs.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/reference/resource-configs/docs.md b/website/docs/reference/resource-configs/docs.md index d300979a826..c5e35dd64f4 100644 --- a/website/docs/reference/resource-configs/docs.md +++ b/website/docs/reference/resource-configs/docs.md @@ -108,7 +108,9 @@ macros: show: true | false ``` + Also refer to [macro properties](/reference/macro-properties). + From accbc41a38ae612ffca5d20d1bf564f5dca8ff0e Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Mon, 13 Nov 2023 09:52:13 -0800 Subject: [PATCH 23/23] Fixing set up ci forwarder (#4453) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## What are you changing in this pull request and why? Fixing link so old search goes to an actual page for https://docs.getdbt.com/guides/orchestration/set-up-ci/lint-on-push. It was forwarding to `https://docs.getdbt.com/%20/guides/set-up-ci` but now forwards correctly to `https://docs.getdbt.com/guides/set-up-ci` ❓ One question for reviewers: Is this forwarded link helpful? I wavered between directly linking to Step 4 for SQL Fluff and linking to the entire guide. I opted for the guide because it feels less fragile. --- website/vercel.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/vercel.json b/website/vercel.json index 7c054b0947e..7b240c35553 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -434,7 +434,7 @@ }, { "source": "/guides/orchestration/set-up-ci/lint-on-push", - "destination": " /guides/set-up-ci", + "destination": "/guides/set-up-ci", "permanent": true }, {