From 64c81f267d7b2b3269599676839395f4fe88d830 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 8 Feb 2024 11:46:29 +0000 Subject: [PATCH 1/5] adding 'new' flag --- website/docs/docs/build/metrics-overview.md | 2 +- website/docs/docs/build/saved-queries.md | 2 +- .../docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md | 2 +- website/docs/docs/use-dbt-semantic-layer/exports.md | 4 +++- 4 files changed, 6 insertions(+), 4 deletions(-) diff --git a/website/docs/docs/build/metrics-overview.md b/website/docs/docs/build/metrics-overview.md index 4d74634a4b8..b5178076eda 100644 --- a/website/docs/docs/build/metrics-overview.md +++ b/website/docs/docs/build/metrics-overview.md @@ -40,7 +40,7 @@ metrics: This page explains the different supported metric types you can add to your dbt project. -### Conversion metrics +### Conversion metrics [Conversion metrics](/docs/build/conversion) help you track when a base event and a subsequent conversion event occurs for an entity within a set time period. diff --git a/website/docs/docs/build/saved-queries.md b/website/docs/docs/build/saved-queries.md index 6a623ad92a3..720f6386502 100644 --- a/website/docs/docs/build/saved-queries.md +++ b/website/docs/docs/build/saved-queries.md @@ -18,7 +18,7 @@ Saved queries are distinct from [exports](/docs/use-dbt-semantic-layer/exports), | **Purpose** | To materialize saved queries in your data platform and expose metrics and dimensions as a view or table. | To define and manage common Semantic Layer queries in YAML, which includes metrics and dimensions. | | **Usage** | Automatically runs saved queries and materializes them within your data platform. Exports count towards [queried metrics](/docs/cloud/billing#what-counts-as-a-queried-metric) usage.

**Example**: Creating a weekly aggregated table for active user metrics, automatically updated and stored in the data platform. | Used for organizing and reusing common MetricFlow queries within dbt projects.


**Example**: Group related metrics together for better organization, and include commonly uses dimensions and filters. | For materializing query results in the data platform. | | **Integration** | Must have the dbt Semantic Layer configured in your dbt project.

Tightly integrated with the [MetricFlow Server](/docs/use-dbt-semantic-layer/sl-architecture#components) and dbt Cloud's job scheduler. | Integrated into the dbt and managed alongside other dbt nodes. | -| **Configuration** | Configured within dbt Cloud environment and job scheduler settings. | Defined in YAML format within dbt project files. | +| **Configuration** | Defined within the `saved_queries` configuration. Set up within the dbt Cloud environment and job scheduler settings. | Defined in YAML format within dbt project files. | All metrics in a saved query need to use the same dimensions in the `group_by` or `where` clauses. The following is an example of a saved query: diff --git a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md index a369c5653cd..e479719e4f0 100644 --- a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md +++ b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md @@ -11,6 +11,6 @@ You can now use the [exports](/docs/use-dbt-semantic-layer/exports) feature with By exposing tables of metrics and dimensions, exports enable you to integrate with additional tools that don't natively connect with the dbt Semantic Layer, such as PowerBI. -Exports are available for dbt Cloud [Team or Enterprise](https://www.getdbt.com/pricing/) plans on dbt versions 1.7 or newer. +Exports are available for dbt Cloud [Team or Enterprise](https://www.getdbt.com/pricing/) plans on dbt versions 1.7 or newer. Refer to the [exports blog](https://www.getdbt.com/blog/announcing-exports-for-the-dbt-semantic-layer) for more details. diff --git a/website/docs/docs/use-dbt-semantic-layer/exports.md b/website/docs/docs/use-dbt-semantic-layer/exports.md index 7497cde0259..b4c2618e456 100644 --- a/website/docs/docs/use-dbt-semantic-layer/exports.md +++ b/website/docs/docs/use-dbt-semantic-layer/exports.md @@ -4,6 +4,8 @@ description: "Use exports to materialize tables to the data platform on a schedu sidebar_label: "Materialize with exports" --- +# Materialize queries with exports + The exports feature in the dbt Semantic Layer enhances the [saved queries](/docs/build/saved-queries) by allowing you to materialize commonly used queries directly within your data platform. While saved queries are a way to save and reuse commonly used queries in MetricFlow, exports take this functionality a step further by: @@ -29,7 +31,7 @@ Essentially, exports are like any other table in your data platform. They enable | **Purpose** | To materialize saved queries in your data platform and expose metrics and dimensions as a view or table. | To define and manage common Semantic Layer queries in YAML, including metrics and dimensions. | | **Usage** | Automatically runs saved queries and materializes them within your data platform. Exports count towards [queried metrics](/docs/cloud/billing#what-counts-as-a-queried-metric) usage.

Example: Create a weekly aggregated table for active user metrics, automatically updated and stored in the data platform. | Used for organizing and reusing common MetricFlow queries within dbt projects.


Example: Group related metrics together for better organization, and include commonly used dimensions and filters. | For materializing query results in the data platform. | | **Integration** | Must have the dbt Semantic Layer configured in your dbt project.

Tightly integrated with the [MetricFlow Server](/docs/use-dbt-semantic-layer/sl-architecture#components) and dbt Cloud's job scheduler. | Integrated into the dbt and managed alongside other dbt nodes. | -| **Configuration** | Defined within the `saved_queries` configuration. Configured within the dbt Cloud environment and job scheduler settings. | Defined in YAML format within dbt project files. | +| **Configuration** | Defined within the `saved_queries` configuration. Set up within the dbt Cloud environment and job scheduler settings. | Defined in YAML format within dbt project files. | ## Define exports From ee2e78339981920d05a24025c0db5d1444625ac7 Mon Sep 17 00:00:00 2001 From: mirnawong1 Date: Thu, 8 Feb 2024 11:53:14 +0000 Subject: [PATCH 2/5] update --- website/docs/docs/dbt-versions/product-lifecycles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/product-lifecycles.md b/website/docs/docs/dbt-versions/product-lifecycles.md index 71f33110eb2..d49c4dc05b7 100644 --- a/website/docs/docs/dbt-versions/product-lifecycles.md +++ b/website/docs/docs/dbt-versions/product-lifecycles.md @@ -18,7 +18,7 @@ Any dbt feature will fall into one of the following lifecycle states: - **Preview (Private or Public):** Preview features are stable and can be considered for production deployments. There may still be some planned additions and modifications to product behaviors before moving to General Availability. We may also introduce new functionality to Preview features that is not backward compatible. Preview features include documentation, technical support, and include service level objectives (SLOs). Features in Preview are generally provided at no extra cost, although they may become paid features in their Generally Available state. -- **Generally Available(GA):** Generally Available features provide stable features that can be considered for production deployments. Service level agreements (SLAs) apply to GA features, and these features include documentation and technical support. +- **Generally Available (GA):** Generally Available features provide stable features that can be considered for production deployments. Service level agreements (SLAs) apply to GA features, and these features include documentation and technical support. - **Deprecated:** Features in this state are not actively worked on or enhanced by dbt Labs and will continue to function as-is until their removal date. From 3c313ea1df1b77745707b9af920f913bf86746f0 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 8 Feb 2024 15:59:12 +0000 Subject: [PATCH 3/5] Update website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md --- .../docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md index e479719e4f0..bccff7995b1 100644 --- a/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md +++ b/website/docs/docs/dbt-versions/release-notes/72-Feb-2024/exports-rn.md @@ -11,6 +11,6 @@ You can now use the [exports](/docs/use-dbt-semantic-layer/exports) feature with By exposing tables of metrics and dimensions, exports enable you to integrate with additional tools that don't natively connect with the dbt Semantic Layer, such as PowerBI. -Exports are available for dbt Cloud [Team or Enterprise](https://www.getdbt.com/pricing/) plans on dbt versions 1.7 or newer. Refer to the [exports blog](https://www.getdbt.com/blog/announcing-exports-for-the-dbt-semantic-layer) for more details. +Exports are available for dbt Cloud multi-tenant [Team or Enterprise](https://www.getdbt.com/pricing/) plans on dbt versions 1.7 or newer. Refer to the [exports blog](https://www.getdbt.com/blog/announcing-exports-for-the-dbt-semantic-layer) for more details. From ccba94b58b07daf618afad7bcdcf74955b149bd1 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 8 Feb 2024 16:00:01 +0000 Subject: [PATCH 4/5] Update exports.md --- website/docs/docs/use-dbt-semantic-layer/exports.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/exports.md b/website/docs/docs/use-dbt-semantic-layer/exports.md index b4c2618e456..ac76d1d8c46 100644 --- a/website/docs/docs/use-dbt-semantic-layer/exports.md +++ b/website/docs/docs/use-dbt-semantic-layer/exports.md @@ -13,11 +13,11 @@ While saved queries are a way to save and reuse commonly used queries in MetricF - Enabling you to materialize these queries within your data platform using dbt Cloud. - Proving an integration path for tools that don't natively support the dbt Semantic Layer by exposing tables of metrics and dimensions. -Essentially, exports are like any other table in your data platform. They enable you to query metric definitions through any SQL interface or connect to downstream tools without needing a first-class Semantic Layer integration. Refer to [Available integrations](/docs/use-dbt-semantic-layer/avail-sl-integrations) for more information. +Essentially, exports are like any other table in your data platform. They enable you to query metric definitions through any SQL interface or connect to downstream tools without a first-class Semantic Layer integration. Refer to [Available integrations](/docs/use-dbt-semantic-layer/avail-sl-integrations) for more information. ## Prerequisites -- You have a dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. +- You have a multi-tenant dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. (Single tenant is not supported at this time) - You are on [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.7 or newer. - You have the dbt Semantic Layer [configured](/docs/use-dbt-semantic-layer/setup-sl) in your dbt project. - You have a dbt Cloud environment with a [Job scheduler](/docs/deploy/job-scheduler) enabled. From fcab24af89416b154a14498b9f51e31c2dfe5d1a Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 8 Feb 2024 16:00:23 +0000 Subject: [PATCH 5/5] Update website/docs/docs/use-dbt-semantic-layer/exports.md --- website/docs/docs/use-dbt-semantic-layer/exports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/use-dbt-semantic-layer/exports.md b/website/docs/docs/use-dbt-semantic-layer/exports.md index ac76d1d8c46..e7cb767723f 100644 --- a/website/docs/docs/use-dbt-semantic-layer/exports.md +++ b/website/docs/docs/use-dbt-semantic-layer/exports.md @@ -17,7 +17,7 @@ Essentially, exports are like any other table in your data platform. They enable ## Prerequisites -- You have a multi-tenant dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. (Single tenant is not supported at this time) +- You have a multi-tenant dbt Cloud account on a [Team or Enterprise](https://www.getdbt.com/pricing/) plan. (Single-tenant is not supported at this time) - You are on [dbt version](/docs/dbt-versions/upgrade-core-in-cloud) 1.7 or newer. - You have the dbt Semantic Layer [configured](/docs/use-dbt-semantic-layer/setup-sl) in your dbt project. - You have a dbt Cloud environment with a [Job scheduler](/docs/deploy/job-scheduler) enabled.