From c90baff408f50daacdd23788952da1686c048bc6 Mon Sep 17 00:00:00 2001 From: marcelobour <117930774+marcelobour@users.noreply.github.com> Date: Wed, 11 Dec 2024 23:35:00 -0300 Subject: [PATCH 1/4] Update about in --favor-state Note While it's clear that --favor-state skips step 1, mentioning only "production metadata" without addressing staging metadata could be misleading. --- 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 ea059ed3e27..2cb17747111 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -19,7 +19,7 @@ When using `--defer`, dbt Cloud will follow this order of execution for resolvin 2. If a development version doesn't exist, dbt uses the staging locations of parent relations based on metadata from the staging environment. 3. If both a development and staging version doesn't exist, dbt uses the production locations of parent relations based on metadata from the production environment. -**Note:** Passing the `--favor-state` flag will always resolve refs using production metadata, regardless of the presence of a development relation, skipping step #1. +**Note:** Passing the `--favor-state` flag will always resolve refs using staging metadaba if it exists, else production metadata, regardless of the presence of a development relation, skipping step #1. For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle. From 197e97c85edfcb8f24b6f704bc1fb05fdf6d19c1 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 16 Dec 2024 10:28:41 +0000 Subject: [PATCH 2/4] add semantic models and saved queries to about dbt projects page this pr adds semantic models and saved queries to the 'about dbt projects' page, which lists all the resources supported int eh dbt_project.yml --- website/docs/docs/build/projects.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/docs/build/projects.md b/website/docs/docs/build/projects.md index a65d4773ac6..4732dbe6da7 100644 --- a/website/docs/docs/build/projects.md +++ b/website/docs/docs/build/projects.md @@ -22,6 +22,8 @@ At a minimum, all a project needs is the `dbt_project.yml` project configuration | [metrics](/docs/build/build-metrics-intro) | A way for you to define metrics for your project. | | [groups](/docs/build/groups) | Groups enable collaborative node organization in restricted collections. | | [analysis](/docs/build/analyses) | A way to organize analytical SQL queries in your project such as the general ledger from your QuickBooks. | +| [semantic models](/docs/build/semantic-models) | Semantic models define the foundational data relationships in [MetricFlow](/docs/build/about-metricflow) and the [dbt Semantic Layer](/docs/use-dbt-semantic-layer/dbt-sl), enabling you to query metrics using a semantic graph. | +| [saved queries](/docs/build/saved-queries) | Saved queries organize reusable queries by grouping metrics, dimensions, and filters into nodes visible in the dbt DAG. | When building out the structure of your project, you should consider these impacts on your organization's workflow: From 984ce495123a6bee090dcb7bce0ae2f8d922040d Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 16 Dec 2024 10:32:24 +0000 Subject: [PATCH 3/4] remove preview from athena this pr removes the preview pill from amazon athena --- .../docs/docs/cloud/connect-data-platform/about-connections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/cloud/connect-data-platform/about-connections.md b/website/docs/docs/cloud/connect-data-platform/about-connections.md index 6497e86de89..b9b2c18aced 100644 --- a/website/docs/docs/cloud/connect-data-platform/about-connections.md +++ b/website/docs/docs/cloud/connect-data-platform/about-connections.md @@ -8,7 +8,7 @@ pagination_prev: null --- dbt Cloud can connect with a variety of data platform providers including: - [AlloyDB](/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb) -- [Amazon Athena](/docs/cloud/connect-data-platform/connect-amazon-athena) +- [Amazon Athena](/docs/cloud/connect-data-platform/connect-amazon-athena) - [Amazon Redshift](/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb) - [Apache Spark](/docs/cloud/connect-data-platform/connect-apache-spark) - [Azure Synapse Analytics](/docs/cloud/connect-data-platform/connect-azure-synapse-analytics) From 8e54711e0bf073cdf435f775b25896f0b9580b4d Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Mon, 16 Dec 2024 13:58:52 +0000 Subject: [PATCH 4/4] Update website/docs/docs/cloud/about-cloud-develop-defer.md --- 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 2cb17747111..d1685c42cba 100644 --- a/website/docs/docs/cloud/about-cloud-develop-defer.md +++ b/website/docs/docs/cloud/about-cloud-develop-defer.md @@ -19,7 +19,7 @@ When using `--defer`, dbt Cloud will follow this order of execution for resolvin 2. If a development version doesn't exist, dbt uses the staging locations of parent relations based on metadata from the staging environment. 3. If both a development and staging version doesn't exist, dbt uses the production locations of parent relations based on metadata from the production environment. -**Note:** Passing the `--favor-state` flag will always resolve refs using staging metadaba if it exists, else production metadata, regardless of the presence of a development relation, skipping step #1. +**Note:** Passing the `--favor-state` flag will always resolve refs using staging metadata if available; otherwise, it defaults to production metadata regardless of the presence of a development relation, skipping step #1. For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle.