Skip to content

Commit

Permalink
Small fix for wording for on_configuration_change (#5213)
Browse files Browse the repository at this point in the history
[Preview](https://docs-getdbt-com-git-dbeatty10-patch-4-dbt-labs.vercel.app/reference/resource-configs/on_configuration_change)

## What are you changing in this pull request and why?

The sentence is misworded, and this is an attempt to fix it.

This PR needs someone on the Adapters team to review for technical
correctness.

## Checklist
- [x] 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.
  • Loading branch information
nghi-ly authored Apr 2, 2024
2 parents dcffb6b + 202bfd6 commit 6335a34
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This functionality is currently only supported for [materialized views](/docs/bu

The `on_configuration_change` config has three settings:
- `apply` (default) — Attempt to update the existing database object if possible, avoiding a complete rebuild.
- *Note:* If any individual configuration change requires a full refresh, a full refresh be performed in lieu of individual alter statements.
- *Note:* If any individual configuration change requires a full refresh, a full refresh is performed in lieu of individual alter statements.
- `continue` — Allow runs to continue while also providing a warning that the object was left untouched.
- *Note:* This could result in downstream failures as those models may depend on these unimplemented changes.
- `fail` — Force the entire run to fail if a change is detected.
Expand Down

0 comments on commit 6335a34

Please sign in to comment.