From bdfcdbb4e48a038dbf3ab70c44d0be8930be02c6 Mon Sep 17 00:00:00 2001
From: Amy Chen <46451573+amychen1776@users.noreply.github.com>
Date: Wed, 7 Feb 2024 07:54:25 -0500
Subject: [PATCH 1/6] Update fabric-setup.md
---
website/docs/docs/core/connect-data-platform/fabric-setup.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/docs/docs/core/connect-data-platform/fabric-setup.md b/website/docs/docs/core/connect-data-platform/fabric-setup.md
index 5180d65ebb9..3caab76301f 100644
--- a/website/docs/docs/core/connect-data-platform/fabric-setup.md
+++ b/website/docs/docs/core/connect-data-platform/fabric-setup.md
@@ -15,7 +15,7 @@ meta:
:::info
-Below is a guide for use with [Synapse Data Warehouse](https://learn.microsoft.com/en-us/fabric/data-warehouse/data-warehousing#synapse-data-warehouse), a new product within Microsoft Fabric.
+Below is a guide for use with [Synapse Data Warehouse](https://learn.microsoft.com/en-us/fabric/data-warehouse/data-warehousing#synapse-data-warehouse), a new product within Microsoft Fabric. The adapter currently only supports connecting to a warehouse and not a lakehouse endpoint. You can access data in your lakehouse via the warehouse if you are in the same workspace.
To learn how to set up dbt with Azure Synapse Dedicated Pools, refer to [Microsoft Azure Synapse DWH setup](/docs/core/connect-data-platform/azuresynapse-setup).
From d3c6d2f5c057fa945c9e730ff224c39abc00e5aa Mon Sep 17 00:00:00 2001
From: ialdg <39755524+ialdg@users.noreply.github.com>
Date: Sun, 11 Feb 2024 07:05:20 +0100
Subject: [PATCH 2/6] Update data-tests.md. Solving double negative.
Hi.
Since the tests looks for negative amount records, why not say so instead of using a double negative, which is not the easiest to read and involves longer code?
Regards.
IL.
---
website/docs/docs/build/data-tests.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/docs/docs/build/data-tests.md b/website/docs/docs/build/data-tests.md
index d981d7e272d..f06e05f6af8 100644
--- a/website/docs/docs/build/data-tests.md
+++ b/website/docs/docs/build/data-tests.md
@@ -49,7 +49,7 @@ select
sum(amount) as total_amount
from {{ ref('fct_payments' )}}
group by 1
-having not(total_amount >= 0)
+having total_amount < 0
```
From 902aeb1531e1b84440c9d11a6b8970cd944cad74 Mon Sep 17 00:00:00 2001
From: ialdg <39755524+ialdg@users.noreply.github.com>
Date: Sun, 11 Feb 2024 07:40:02 +0100
Subject: [PATCH 3/6] Update data-tests.md. Correct misspelling.
Hi.
I just proposed a misspelling correction.
Regards.
IL.
---
website/docs/docs/build/data-tests.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/docs/docs/build/data-tests.md b/website/docs/docs/build/data-tests.md
index d981d7e272d..10a8b4a1539 100644
--- a/website/docs/docs/build/data-tests.md
+++ b/website/docs/docs/build/data-tests.md
@@ -247,7 +247,7 @@ This workflow allows you to query and examine failing records much more quickly
-Note that, if you elect to store test failures:
+Note that, if you select to store test failures:
* Test result tables are created in a schema suffixed or named `dbt_test__audit`, by default. It is possible to change this value by setting a `schema` config. (For more details on schema naming, see [using custom schemas](/docs/build/custom-schemas).)
- A test's results will always **replace** previous failures for the same test.
From 7dea0900dd5c0a94af277eac37bb97da163feffc Mon Sep 17 00:00:00 2001
From: Cameron Afzal
Date: Mon, 12 Feb 2024 08:12:00 -0800
Subject: [PATCH 4/6] Correct state requirement / caveat for clarity
---
website/docs/docs/dbt-cloud-apis/project-state.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/docs/docs/dbt-cloud-apis/project-state.md b/website/docs/docs/dbt-cloud-apis/project-state.md
index 62136b35463..78dff4309db 100644
--- a/website/docs/docs/dbt-cloud-apis/project-state.md
+++ b/website/docs/docs/dbt-cloud-apis/project-state.md
@@ -81,5 +81,5 @@ Here are some limitations of the state representation in the Discovery API:
- Users must access the default production environment to know the latest state of a project.
- The API gets the definition from the latest manifest generated in a given deployment environment, but that often won’t reflect the latest project code state.
- Compiled code results may be outdated depending on dbt Cloud run step order and failures.
-- Catalog info can be outdated, or incomplete (in the applied state), based on if/when docs were last generated.
+- Catalog info can be outdated, or incomplete (in the applied state), based on if/when `docs generate` was last run.
- Source freshness checks can be out of date (in the applied state) depending on when the command was last run, and it’s not included in `build`.
From c56d34fcc901557574111946ef8e47fdb033feb4 Mon Sep 17 00:00:00 2001
From: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
Date: Mon, 12 Feb 2024 11:29:34 -0500
Subject: [PATCH 5/6] Update data-tests.md
Clarifying language to match changes
---
website/docs/docs/build/data-tests.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/docs/docs/build/data-tests.md b/website/docs/docs/build/data-tests.md
index af738054fc2..0806842a85c 100644
--- a/website/docs/docs/build/data-tests.md
+++ b/website/docs/docs/build/data-tests.md
@@ -43,7 +43,7 @@ These tests are defined in `.sql` files, typically in your `tests` directory (as
```sql
-- Refunds have a negative amount, so the total amount should always be >= 0.
--- Therefore return records where this isn't true to make the test fail
+-- Therefore return records where total_amount < 0 to make the test fail.
select
order_id,
sum(amount) as total_amount
From da7724fc3f11e1dc990ac418706b0f2fd8f77776 Mon Sep 17 00:00:00 2001
From: "Leona B. Campbell" <3880403+runleonarun@users.noreply.github.com>
Date: Mon, 12 Feb 2024 11:27:40 -0800
Subject: [PATCH 6/6] Update metricflow-commands.md (#4896)
## What are you changing in this pull request and why?
Fixing two minor typos. Thanks @kbrock91 for spotting!
## Checklist
- [ ] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] For [docs
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#about-versioning),
review how to [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content).
- [ ] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."
Adding or removing pages (delete if not applicable):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/static/_redirects`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages
---
website/docs/docs/build/metricflow-commands.md | 2 +-
website/docs/docs/build/saved-queries.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/website/docs/docs/build/metricflow-commands.md b/website/docs/docs/build/metricflow-commands.md
index 675a2d056ac..4693aa1a774 100644
--- a/website/docs/docs/build/metricflow-commands.md
+++ b/website/docs/docs/build/metricflow-commands.md
@@ -75,7 +75,7 @@ You can use the `dbt sl` prefix before the command name to execute them in the d
- [`list dimensions`](#list) — Lists unique dimensions for metrics.
- [`list dimension-values`](#list-dimension-values) — List dimensions with metrics.
- [`list entities`](#list-entities) — Lists all unique entities.
-- [`list saved queries`)(#list-saved-queries) — Lists available saved queries. Use the `--show-exports` flag to display each export listed under a saved query.
+- [`list saved queries`](#list-saved-queries) — Lists available saved queries. Use the `--show-exports` flag to display each export listed under a saved query.
- [`query`](#query) — Query metrics, saved queries, and dimensions you want to see in the command line interface. Refer to [query examples](#query-examples) to help you get started.