Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Redshift behavior change: restrict_direct_pg_catalog_access #6082

Merged
merged 5 commits into from
Sep 18, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions website/docs/reference/global-configs/behavior-changes.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -121,3 +122,11 @@ on-run-start:
- '{{ ... if flags.WHICH != 'freshness' }}'
```
</File>

## Adapter-specific behavior changes

mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
### [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`.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved

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.
mirnawong1 marked this conversation as resolved.
Show resolved Hide resolved
Loading