From 4dc549822ea8e6e208e2dcb5d83f1be29e8b8c35 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Wed, 18 Sep 2024 11:11:57 +0100
Subject: [PATCH 1/3] Update saved-queries.md
---
website/docs/docs/build/saved-queries.md | 39 +++++++++++++-----------
1 file changed, 21 insertions(+), 18 deletions(-)
diff --git a/website/docs/docs/build/saved-queries.md b/website/docs/docs/build/saved-queries.md
index e9beffca15f..0cf42f85080 100644
--- a/website/docs/docs/build/saved-queries.md
+++ b/website/docs/docs/build/saved-queries.md
@@ -69,6 +69,26 @@ Use saved queries to define and manage common Semantic Layer queries in YAML, in
In your saved query config, you can also leverage [caching](/docs/use-dbt-semantic-layer/sl-cache) with the dbt Cloud job scheduler to cache common queries, speed up performance, and reduce compute costs.
+
+
+ #### Project-level saved queries
+
+To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
+
+
+
+```yaml
+saved-queries:
+ my_saved_query:
+ config:
+ +cache:
+ enabled: true
+```
+
+
+For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+
+
@@ -102,24 +122,7 @@ saved_queries:
```
-Note, you can set `export_as` to both the saved query and the exports [config](/reference/resource-properties/config), with the exports config value taking precedence. If a key isn't set in the exports config, it will inherit the saved query config value.
-
-#### Project-level saved queries
-
-To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
-
-
-
-```yaml
-saved-queries:
- my_saved_query:
- config:
- +cache:
- enabled: true
-```
-
-
-For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+Note, that you can set `export_as` to both the saved query and the exports [config](/reference/resource-properties/config), with the exports config value taking precedence. If a key isn't set in the exports config, it will inherit the saved query config value.
#### Where clause
From 9c92bbb44a68824a070f11f1ce95d1f0f2965f65 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Thu, 19 Sep 2024 12:11:52 +0100
Subject: [PATCH 2/3] Update saved-queries.md
---
website/docs/docs/build/saved-queries.md | 40 ++++++++++++------------
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/website/docs/docs/build/saved-queries.md b/website/docs/docs/build/saved-queries.md
index 0cf42f85080..92afdfa85f4 100644
--- a/website/docs/docs/build/saved-queries.md
+++ b/website/docs/docs/build/saved-queries.md
@@ -69,26 +69,6 @@ Use saved queries to define and manage common Semantic Layer queries in YAML, in
In your saved query config, you can also leverage [caching](/docs/use-dbt-semantic-layer/sl-cache) with the dbt Cloud job scheduler to cache common queries, speed up performance, and reduce compute costs.
-
-
- #### Project-level saved queries
-
-To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
-
-
-
-```yaml
-saved-queries:
- my_saved_query:
- config:
- +cache:
- enabled: true
-```
-
-
-For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
-
-
@@ -144,6 +124,26 @@ filter: |
+
+
+#### Project-level saved queries
+
+To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
+
+
+
+```yaml
+saved-queries:
+ my_saved_query:
+ config:
+ +cache:
+ enabled: true
+```
+
+
+For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+
+
From 500614b72f435e7cc456f0a35e3e7373c847cd19 Mon Sep 17 00:00:00 2001
From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com>
Date: Thu, 19 Sep 2024 12:25:20 +0100
Subject: [PATCH 3/3] Update saved-queries.md
---
website/docs/docs/build/saved-queries.md | 40 ++++++++++++------------
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/website/docs/docs/build/saved-queries.md b/website/docs/docs/build/saved-queries.md
index 92afdfa85f4..91595bde849 100644
--- a/website/docs/docs/build/saved-queries.md
+++ b/website/docs/docs/build/saved-queries.md
@@ -124,26 +124,6 @@ filter: |
-
-
-#### Project-level saved queries
-
-To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
-
-
-
-```yaml
-saved-queries:
- my_saved_query:
- config:
- +cache:
- enabled: true
-```
-
-
-For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
-
-
@@ -174,6 +154,26 @@ saved_queries:
+
+
+#### Project-level saved queries
+
+To enable saved queries at the project level, you can set the `saved-queries` configuration in the [`dbt_project.yml` file](/reference/dbt_project.yml). This saves you time in configuring saved queries in each file:
+
+
+
+```yaml
+saved-queries:
+ my_saved_query:
+ config:
+ +cache:
+ enabled: true
+```
+
+
+For more information on `dbt_project.yml` and config naming conventions, see the [dbt_project.yml reference page](/reference/dbt_project.yml#naming-convention).
+
+
To build `saved_queries`, use the [`--resource-type` flag](/reference/global-configs/resource-type) and run the command `dbt build --resource-type saved_query`.
## Configure exports