clarify defer behavior #4435
Merged
clarify defer behavior #4435
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
|
Looks good to me! |
sophiad96
approved these changes
Nov 10, 2023
| Both the dbt Cloud IDE and the dbt Cloud CLI allow users to natively defer to production metadata directly in their development workflows, dramatically reducing development time and warehouse spend by preventing unnecessary model builds. | ||
| By default, dbt follows these rules: | ||
|
|
||
| - Defers to the production environment when there's no development schema. |
There was a problem hiding this comment.
Suggested change
| - Defers to the production environment when there's no development schema. | |
| - Resolves `{{ ref() }}` functions using the production locations for the parents of selected models using metadata from the production environment. |
There was a problem hiding this comment.
- dbt uses the production locations of parent models to resolve
{{ ref() }}functions, based on metadata from the production environment
| By default, dbt follows these rules: | ||
|
|
||
| - Defers to the production environment when there's no development schema. | ||
| - If a development schema exists, dbt will prioritize those changes, which minimizes development time and avoids unnecessary model builds. |
There was a problem hiding this comment.
Suggested change
| - If a development schema exists, dbt will prioritize those changes, which minimizes development time and avoids unnecessary model builds. | |
| - If a development version of a deferred model exists, dbt preferentially use that table when resolving the reference. | |
| - Passing the `--favor-state` flag will override this behavior, and _always_ resolve refs using the production metadata, regardless of the presence of a development relation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sophia raised a great question about defer's behavior, which users were reaching out to.
adding this info to the docs so it's clear