From 0dd1d2863907a7e847d11a14e9c28d72608a4beb Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 9 Nov 2023 12:43:08 +0000 Subject: [PATCH 01/27] 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/27] 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/27] 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/27] 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/27] 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/27] 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 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 07/27] 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 08/27] 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 09/27] 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 10/27] 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 11/27] 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 12/27] 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 9abe20d09b5a67f058591ec7244571f70b6612ab Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 11:40:10 +0000 Subject: [PATCH 13/27] Update meta.md fix header --- website/docs/reference/resource-configs/meta.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/reference/resource-configs/meta.md b/website/docs/reference/resource-configs/meta.md index 9ccf2cc60dc..bc0c0c7c041 100644 --- a/website/docs/reference/resource-configs/meta.md +++ b/website/docs/reference/resource-configs/meta.md @@ -277,8 +277,8 @@ seeds: select 1 as id ``` - - +
+ ### Assign owner in the dbt_project.yml as a config property From 39449daf6f9e4211af4b43346d2efd249140bda9 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Mon, 13 Nov 2023 15:44:18 +0000 Subject: [PATCH 14/27] tweak defer lanuge --- .../docs/docs/cloud/about-cloud-develop-defer.md | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 1861a6d8a79..302a3548351 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -9,16 +9,12 @@ 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. -By default, dbt follows these rules: +Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows. 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 development schema, `--favor-state` is an alternative to defer. +- dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. +- If a development version of a deferred model exists, dbt preferentially uses that table when resolving the reference. +- Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag will override this behavior and _always_ resolve refs using the production metadata, regardless of the presence of a development relation. + - 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 development schema at the start and end of your development cycle. From 5467027d0d2f4c8c7d2c65d236e48a1c49397ddd Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 15:49:59 +0000 Subject: [PATCH 15/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: dave-connors-3 <73915542+dave-connors-3@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 302a3548351..f0fcaec9f39 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -12,7 +12,7 @@ pagination_next: "docs/cloud/cloud-cli-installation" Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows. By default, dbt follows these rules: - dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. -- If a development version of a deferred model exists, dbt preferentially uses that table when resolving the reference. +- If a development version of a deferred model exists, dbt preferentially uses that database location when resolving the reference. - Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag will override this behavior and _always_ resolve refs using the production metadata, regardless of the presence of a development relation. - If facing issues with outdated tables in the development schema, `--favor-state` is an alternative to defer. From caa28652e56f0bff48a13029262c6a035624ad16 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 15:52:45 +0000 Subject: [PATCH 16/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: dave-connors-3 <73915542+dave-connors-3@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 1 - 1 file changed, 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index f0fcaec9f39..fca09530f62 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -14,7 +14,6 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr - dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. - If a development version of a deferred model exists, dbt preferentially uses that database location when resolving the reference. - Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag will override this behavior and _always_ resolve refs using the production metadata, regardless of the presence of a development relation. - - 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 development schema at the start and end of your development cycle. From 2ea6ba1b02fd369d7ff33cd1e5b20fd08f8b6983 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 15:53:55 +0000 Subject: [PATCH 17/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md --- website/docs/docs/cloud/about-cloud-develop-defer.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index fca09530f62..d261a990b90 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -9,7 +9,9 @@ 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. -Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows. By default, dbt follows these rules: +Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows. + +By default, dbt follows these rules: - dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. - If a development version of a deferred model exists, dbt preferentially uses that database location when resolving the reference. From 9a9118b827f42ea7983027ec62cd081ca2659063 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 17:46:04 +0000 Subject: [PATCH 18/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index d261a990b90..0c961cf0db1 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -15,7 +15,7 @@ By default, dbt follows these rules: - dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. - If a development version of a deferred model exists, dbt preferentially uses that database location when resolving the reference. -- Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag will override this behavior and _always_ resolve refs using the production metadata, regardless of the presence of a development relation. +- Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag overrides the default behavior and _always_ resolve refs using production metadata, regardless of the presence of a development relation. For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle. From e24ee7074cd5ae781d4a8027d116b49c6b6842f7 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 17:46:10 +0000 Subject: [PATCH 19/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 0c961cf0db1..5d3b76c7430 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -14,7 +14,7 @@ Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to pr By default, dbt follows these rules: - dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment. -- If a development version of a deferred model exists, dbt preferentially uses that database location when resolving the reference. +- If a development version of a deferred model exists, dbt preferentially uses the development database location when resolving the reference. - Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag overrides the default behavior and _always_ resolve refs using production metadata, regardless of the presence of a development relation. For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle. From c5c4a69d028595eb0fd556475a493afaf5bd2de9 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 17:46:18 +0000 Subject: [PATCH 20/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 5d3b76c7430..0158ed8a7eb 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -7,7 +7,7 @@ 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). dbt powers this by using a production manifest for comparison, and resolves 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. From 2cba7d1baac86cf4796158f748b57b1395646163 Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 13 Nov 2023 17:46:25 +0000 Subject: [PATCH 21/27] Update website/docs/docs/cloud/about-cloud-develop-defer.md Co-authored-by: Leona B. Campbell <3880403+runleonarun@users.noreply.github.com> --- website/docs/docs/cloud/about-cloud-develop-defer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/about-cloud-develop-defer.md b/website/docs/docs/cloud/about-cloud-develop-defer.md index 0158ed8a7eb..37bfaacfd0c 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -9,7 +9,7 @@ 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). dbt powers this by using a production manifest for comparison, and resolves 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. +Both the dbt Cloud IDE and the dbt Cloud CLI enable users to natively defer to production metadata directly in their development workflows. By default, dbt follows these rules: 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 22/27] 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 }, { From 6983bdb43f7ced6a923c2e0dfa73391187cac3f0 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 13 Nov 2023 13:15:28 -0500 Subject: [PATCH 23/27] Correcting grain: MONTH syntax --- website/docs/docs/dbt-cloud-apis/sl-graphql.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/website/docs/docs/dbt-cloud-apis/sl-graphql.md b/website/docs/docs/dbt-cloud-apis/sl-graphql.md index 0e39f50f60a..71ad175c11c 100644 --- a/website/docs/docs/dbt-cloud-apis/sl-graphql.md +++ b/website/docs/docs/dbt-cloud-apis/sl-graphql.md @@ -282,7 +282,7 @@ mutation { createQuery( environmentId: BigInt! metrics: [{name: "order_total"}] - groupBy: [{name: "metric_time", grain: "month"}] + groupBy: [{name: "metric_time", grain: MONTH}] ) { queryId } @@ -298,7 +298,7 @@ mutation { createQuery( environmentId: BigInt! metrics: [{name: "food_order_amount"}, {name: "order_gross_profit"}] - groupBy: [{name: "metric_time, grain: "month"}, {name: "customer__customer_type"}] + groupBy: [{name: "metric_time, grain: MONTH}, {name: "customer__customer_type"}] ) { queryId } @@ -320,7 +320,7 @@ mutation { createQuery( environmentId: BigInt! metrics:[{name: "order_total"}] - groupBy:[{name: "customer__customer_type"}, {name: "metric_time", grain: "month"}] + groupBy:[{name: "customer__customer_type"}, {name: "metric_time", grain: MONTH}] where:[{sql: "{{ Dimension('customer__customer_type') }} = 'new'"}, {sql:"{{ Dimension('metric_time').grain('month') }} > '2022-10-01'"}] ) { queryId @@ -335,8 +335,8 @@ mutation { createQuery( environmentId: BigInt! metrics: [{name: "order_total"}] - groupBy: [{name: "metric_time", grain: "month"}] - orderBy: [{metric: {name: "order_total"}}, {groupBy: {name: "metric_time", grain: "month"}, descending:true}] + groupBy: [{name: "metric_time", grain: MONTH}] + orderBy: [{metric: {name: "order_total"}}, {groupBy: {name: "metric_time", grain: MONTH}, descending:true}] ) { queryId } @@ -351,7 +351,7 @@ mutation { createQuery( environmentId: BigInt! metrics: [{name:"food_order_amount"}, {name: "order_gross_profit"}] - groupBy: [{name:"metric_time, grain: "month"}, {name: "customer__customer_type"}] + groupBy: [{name:"metric_time, grain: MONTH}, {name: "customer__customer_type"}] limit: 10 ) { queryId From 6f98fdf2396795f3bf99430890623eca3621e807 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 13 Nov 2023 13:30:01 -0500 Subject: [PATCH 24/27] Additional change --- website/docs/docs/dbt-cloud-apis/sl-graphql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-cloud-apis/sl-graphql.md b/website/docs/docs/dbt-cloud-apis/sl-graphql.md index 71ad175c11c..f73007c9a02 100644 --- a/website/docs/docs/dbt-cloud-apis/sl-graphql.md +++ b/website/docs/docs/dbt-cloud-apis/sl-graphql.md @@ -368,7 +368,7 @@ mutation { compileSql( environmentId: BigInt! metrics: [{name:"food_order_amount"} {name:"order_gross_profit"}] - groupBy: [{name:"metric_time, grain:"month"}, {name:"customer__customer_type"}] + groupBy: [{name:"metric_time, grain: MONTH}, {name:"customer__customer_type"}] ) { sql } From c1be1ec66e2713c50c79e78f3e572f06f4f33336 Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 13 Nov 2023 13:45:47 -0500 Subject: [PATCH 25/27] Fixing generic examples on group page --- .../docs/reference/resource-configs/group.md | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/website/docs/reference/resource-configs/group.md b/website/docs/reference/resource-configs/group.md index bce2a72136e..df4d5ab8e3b 100644 --- a/website/docs/reference/resource-configs/group.md +++ b/website/docs/reference/resource-configs/group.md @@ -35,8 +35,8 @@ Support for grouping models was added in dbt Core v1.5 version: 2 models: - - name: model_name - group: finance + - name: MODEL_NAME + group: GROUP_NAME ``` @@ -46,7 +46,7 @@ models: ```yml models: [](resource-path): - +group: finance + +group: GROUP_NAME ``` @@ -57,7 +57,7 @@ models: ```sql {{ config( - group='finance' + group='GROUP_NAME' ) }} select ... @@ -85,7 +85,7 @@ Support for grouping seeds was added in dbt Core v1.5 ```yml models: [](resource-path): - +group: finance + +group: GROUP_NAME ``` @@ -94,8 +94,8 @@ models: ```yml seeds: - - name: [] - group: finance + - name: [SEED_NAME] + group: GROUP_NAME ``` @@ -120,7 +120,7 @@ Support for grouping snapshots was added in dbt Core v1.5 ```yml snapshots: [](resource-path): - +group: finance + +group: GROUP_NAME ``` @@ -131,7 +131,7 @@ snapshots: {% snapshot [snapshot_name](snapshot_name) %} {{ config( - group='finance' + group='GROUP_NAME' ) }} select ... @@ -161,7 +161,7 @@ Support for grouping tests was added in dbt Core v1.5 ```yml tests: [](resource-path): - +group: finance + +group: GROUP_NAME ``` @@ -176,7 +176,7 @@ version: 2 tests: - : config: - group: finance + group: GROUP_NAME ``` @@ -187,7 +187,7 @@ version: 2 {% test () %} {{ config( - group='finance' + group='GROUP_NAME' ) }} select ... @@ -202,7 +202,7 @@ select ... ```sql {{ config( - group='finance' + group='GROUP_NAME' ) }} ``` @@ -220,8 +220,8 @@ select ... version: 2 analyses: - - name: - group: finance + - name: ANALYSIS_NAME + group: GROUP_NAME ``` @@ -244,7 +244,7 @@ Support for grouping metrics was added in dbt Core v1.5 ```yaml metrics: [](resource-path): - [+](plus-prefix)group: finance + [+](plus-prefix)group: GROUP_NAME ``` @@ -255,8 +255,8 @@ metrics: version: 2 metrics: - - name: [] - group: finance + - name: [METRIC_NAME] + group: GROUP_NAME ``` @@ -281,8 +281,8 @@ Support for grouping semantic models has been added in dbt Core v1.7. ```yaml semantic_models: - - name: - group: + - name: SEMANTIC_MODEL_NAME + group: GROUP_NAME ``` @@ -293,7 +293,7 @@ semantic_models: ```yaml semantic-models: [](resource-path): - [+](plus-prefix)group: + [+](plus-prefix)group: GROUP_NAME ``` From 5d55661685b61b6e0f638f4dd1b6c6354ef043ef Mon Sep 17 00:00:00 2001 From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com> Date: Mon, 13 Nov 2023 14:29:48 -0500 Subject: [PATCH 26/27] Updating order of examples --- .../reference/resource-configs/enabled.md | 48 +++++++++---------- .../docs/reference/resource-configs/group.md | 36 +++++++------- 2 files changed, 42 insertions(+), 42 deletions(-) diff --git a/website/docs/reference/resource-configs/enabled.md b/website/docs/reference/resource-configs/enabled.md index d146f229494..552777c5c81 100644 --- a/website/docs/reference/resource-configs/enabled.md +++ b/website/docs/reference/resource-configs/enabled.md @@ -20,6 +20,17 @@ default_value: true }> + + +```yml +models: + [](/reference/resource-configs/resource-path): + +enabled: true | false + +``` + + + ```sql @@ -35,10 +46,15 @@ select ... + + + + + ```yml -models: +seeds: [](/reference/resource-configs/resource-path): +enabled: true | false @@ -48,13 +64,12 @@ models: - - + ```yml -seeds: +snapshots: [](/reference/resource-configs/resource-path): +enabled: true | false @@ -62,10 +77,6 @@ seeds: - - - - ```sql @@ -83,10 +94,14 @@ select ... + + + + ```yml -snapshots: +tests: [](/reference/resource-configs/resource-path): +enabled: true | false @@ -94,10 +109,6 @@ snapshots: - - - - ```sql @@ -125,17 +136,6 @@ select ... - - -```yml -tests: - [](/reference/resource-configs/resource-path): - +enabled: true | false - -``` - - - diff --git a/website/docs/reference/resource-configs/group.md b/website/docs/reference/resource-configs/group.md index bce2a72136e..a096feb0eef 100644 --- a/website/docs/reference/resource-configs/group.md +++ b/website/docs/reference/resource-configs/group.md @@ -29,27 +29,27 @@ Support for grouping models was added in dbt Core v1.5 - + ```yml -version: 2 - models: - - name: model_name - group: finance + [](resource-path): + +group: finance ``` + - + ```yml +version: 2 + models: - [](resource-path): - +group: finance + - name: model_name + group: finance ``` - @@ -277,23 +277,23 @@ Support for grouping semantic models has been added in dbt Core v1.7. - + ```yaml -semantic_models: - - name: - group: - +semantic-models: + [](resource-path): + [+](plus-prefix)group: GROUP_NAME ``` - + ```yaml -semantic-models: - [](resource-path): - [+](plus-prefix)group: +semantic_models: + - name: SEMANTIC_MODEL_NAME + group: GROUP_NAME + ``` From af6e2d1ed53375a818063fc5f46b33208aba200b Mon Sep 17 00:00:00 2001 From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com> Date: Mon, 13 Nov 2023 13:50:03 -0800 Subject: [PATCH 27/27] Adding mesh guide redirects (#4458) ## What are you changing in this pull request and why? I missed the mesh guides redirects when working on the quickstarts project. It was published after I ran the script for the URLs affected by the changes. --- website/vercel.json | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/website/vercel.json b/website/vercel.json index 7b240c35553..269ae29116d 100644 --- a/website/vercel.json +++ b/website/vercel.json @@ -22,6 +22,21 @@ "destination": "/guides/debug-errors", "permanent": true }, + { + "source": "/guides/best-practices/how-we-mesh/mesh-1-intro", + "destination": "/best-practices/how-we-mesh/mesh-1-intro", + "permanent": true + }, + { + "source": "/guides/best-practices/how-we-mesh/mesh-2-structures", + "destination": "/best-practices/how-we-mesh/mesh-2-structures", + "permanent": true + }, + { + "source": "/guides/best-practices/how-we-mesh/mesh-3-implementation", + "destination": "/best-practices/how-we-mesh/mesh-3-implementation", + "permanent": true + }, { "source": "/guides/best-practices/how-we-build-our-metrics/semantic-layer-1-intro", "destination": "/best-practices/how-we-build-our-metrics/semantic-layer-1-intro", @@ -434,7 +449,7 @@ }, { "source": "/guides/orchestration/set-up-ci/lint-on-push", - "destination": "/guides/set-up-ci", + "destination": " /guides/set-up-ci", "permanent": true }, {