From 3642fd8b3eb830e1065f23239bd04e68c84e0955 Mon Sep 17 00:00:00 2001 From: Jeremy Cohen Date: Wed, 18 Sep 2024 10:24:55 +0100 Subject: [PATCH 1/5] Update behavior-changes.md --- .../docs/reference/global-configs/behavior-changes.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index 20f5722b944..ce92c31d2c1 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -61,6 +61,7 @@ When we use dbt Cloud in the following table, we're referring to accounts that h | require_explicit_package_overrides_for_builtin_materializations | 2024.04.141 | 2024.06.192 | 1.6.14, 1.7.14 | 1.8.0 | | require_resource_names_without_spaces | 2024.05.146 | TBD* | 1.8.0 | 1.9.0 | | source_freshness_run_project_hooks | 2024.03.61 | TBD* | 1.8.0 | 1.9.0 | +| [Redshift] restrict_direct_pg_catalog_access | 2024.09.242 | TBD* | dbt-redshift v1.9.0 | 1.9.0 | When the dbt Cloud Maturity is "TBD," it means we have not yet determined the exact date when these flags' default values will change. Affected users will see deprecation warnings in the meantime, and they will receive emails providing advance warning ahead of the maturity date. In the meantime, if you are seeing a deprecation warning, you can either: - Migrate your project to support the new behavior, and then set the flag to `True` to stop seeing the warnings. @@ -121,3 +122,11 @@ on-run-start: - '{{ ... if flags.WHICH != 'freshness' }}' ``` + +## Adapter-specific behavior changes + +### [Redshift] restrict_direct_pg_catalog_access + +Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter. It leveraged several Postgres tables for accessing metadata. When this flag is enabled, instead of using `pg_` tables, the adapter will use either the Redshift API (via the Python client) if available, and otherwise query tables in Redshift's `information_schema`. + +While we don't intend for there to be any user-noticeable behavior changes as a result of this change, out of an abundance of caution, we are gating it behind a behavior-change flag and encouraging users to test it out before it becomes the default for everyone. From d556ff5960982718c44b060779288b002bb1db08 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 18 Sep 2024 10:36:17 +0100 Subject: [PATCH 2/5] Update website/docs/reference/global-configs/behavior-changes.md --- website/docs/reference/global-configs/behavior-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index ce92c31d2c1..e6b418dbcc0 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -127,6 +127,6 @@ on-run-start: ### [Redshift] restrict_direct_pg_catalog_access -Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter. It leveraged several Postgres tables for accessing metadata. When this flag is enabled, instead of using `pg_` tables, the adapter will use either the Redshift API (via the Python client) if available, and otherwise query tables in Redshift's `information_schema`. +Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead. While we don't intend for there to be any user-noticeable behavior changes as a result of this change, out of an abundance of caution, we are gating it behind a behavior-change flag and encouraging users to test it out before it becomes the default for everyone. From 1873c8d23d9b7e67784cca5d445827f8828bbb98 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 18 Sep 2024 10:38:21 +0100 Subject: [PATCH 3/5] Update website/docs/reference/global-configs/behavior-changes.md --- website/docs/reference/global-configs/behavior-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index e6b418dbcc0..dd61866ffd1 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -129,4 +129,4 @@ on-run-start: Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead. -While we don't intend for there to be any user-noticeable behavior changes as a result of this change, out of an abundance of caution, we are gating it behind a behavior-change flag and encouraging users to test it out before it becomes the default for everyone. +While we don't expect any user-noticeable behavior changes due to this change, out of caution we are gating it behind a behavior-change flag and encouraging users to test it before it becomes the default for everyone. From 03acc2c024cf7f8f8c4b23ac318fefd06b781fb3 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 18 Sep 2024 10:39:54 +0100 Subject: [PATCH 4/5] Update website/docs/reference/global-configs/behavior-changes.md --- website/docs/reference/global-configs/behavior-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index dd61866ffd1..8964fe36398 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -127,6 +127,6 @@ on-run-start: ### [Redshift] restrict_direct_pg_catalog_access -Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead. +Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead of using `pg_` tables. While we don't expect any user-noticeable behavior changes due to this change, out of caution we are gating it behind a behavior-change flag and encouraging users to test it before it becomes the default for everyone. From 4527d6b3e5be8315e7347b29eab8acdb3bd68a46 Mon Sep 17 00:00:00 2001 From: Mirna Wong <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 18 Sep 2024 10:41:28 +0100 Subject: [PATCH 5/5] Update website/docs/reference/global-configs/behavior-changes.md --- website/docs/reference/global-configs/behavior-changes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/reference/global-configs/behavior-changes.md b/website/docs/reference/global-configs/behavior-changes.md index 8964fe36398..4abdd7d2104 100644 --- a/website/docs/reference/global-configs/behavior-changes.md +++ b/website/docs/reference/global-configs/behavior-changes.md @@ -124,7 +124,7 @@ on-run-start: ## Adapter-specific behavior changes - +Some adapters may show behavior changes when certain flags are enabled. Refer to the following sections for each respective adapter. ### [Redshift] restrict_direct_pg_catalog_access Originally, the `dbt-redshift` adapter was built on top of the `dbt-postgres` adapter and used Postgres tables for metadata access. With this flag enabled, the adapter will use the Redshift API (through the Python client) if available, or query Redshift's `information_schema` tables instead of using `pg_` tables.