From 2f4c841bb51efb6b5e7399a6596490f9cd7050df Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 24 Apr 2024 14:09:27 -0600 Subject: [PATCH 1/4] Upgrade instructions for model names that contain spaces --- .../docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md index 6460c210958..71af9b12519 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md +++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md @@ -88,6 +88,8 @@ We will begin deprecating support for spaces in dbt model names in v1.8 (raising - Spaces in a model name make it impossible to `--select` the model name because the argument gets split into pieces over spaces very early in the pipeline. - Most warehouses do not accept a table, or other object, with a space in its name. +To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a (https://docs.getdbt.com/docs/build/custom-aliases#usage)[custom alias]. + ## Quick hits - [Global config flags](/reference/global-configs/about-global-configs) are deprecated from the [`profiles.yml`](/docs/core/connect-data-platform/profiles.yml) file and should be moved to the [`dbt_project.yml`](/reference/dbt_project.yml). From 9ea9defe0d018e0d72127313139192c7cbfde2c8 Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 24 Apr 2024 14:22:44 -0600 Subject: [PATCH 2/4] Fix hyperlink --- .../docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md index 71af9b12519..2315b03701f 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md +++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md @@ -88,7 +88,7 @@ We will begin deprecating support for spaces in dbt model names in v1.8 (raising - Spaces in a model name make it impossible to `--select` the model name because the argument gets split into pieces over spaces very early in the pipeline. - Most warehouses do not accept a table, or other object, with a space in its name. -To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a (https://docs.getdbt.com/docs/build/custom-aliases#usage)[custom alias]. +To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [https://docs.getdbt.com/docs/build/custom-aliases#usage](custom alias). ## Quick hits From 7009d3a55e0defe884c5f25894564254a854c24b Mon Sep 17 00:00:00 2001 From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com> Date: Wed, 24 Apr 2024 15:00:51 -0600 Subject: [PATCH 3/4] Really fix the hyperlink this time --- .../docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md index 2315b03701f..208b7530bea 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md +++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md @@ -88,7 +88,7 @@ We will begin deprecating support for spaces in dbt model names in v1.8 (raising - Spaces in a model name make it impossible to `--select` the model name because the argument gets split into pieces over spaces very early in the pipeline. - Most warehouses do not accept a table, or other object, with a space in its name. -To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [https://docs.getdbt.com/docs/build/custom-aliases#usage](custom alias). +To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [custom `alias`](docs/build/custom-aliases#usage). ## Quick hits From e7251aba40141c5b2b0a96cdbf7e580d7eb6a0e8 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Thu, 25 Apr 2024 13:22:14 +0100 Subject: [PATCH 4/4] Update website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md --- .../docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md index 208b7530bea..73950e78565 100644 --- a/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md +++ b/website/docs/docs/dbt-versions/core-upgrade/01-upgrading-to-v1.8.md @@ -88,7 +88,7 @@ We will begin deprecating support for spaces in dbt model names in v1.8 (raising - Spaces in a model name make it impossible to `--select` the model name because the argument gets split into pieces over spaces very early in the pipeline. - Most warehouses do not accept a table, or other object, with a space in its name. -To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [custom `alias`](docs/build/custom-aliases#usage). +To upgrade, replace any spaces in the model file name with an underscore and update any associated YAML that contains the model name to match. You can keep spaces in the database table name by configuring a [custom `alias`](/docs/build/custom-aliases#usage). ## Quick hits