Skip to content

Commit

Permalink
Merge branch 'current' into add-custom-date
Browse files Browse the repository at this point in the history
  • Loading branch information
mirnawong1 authored Nov 15, 2024
2 parents 3fb5435 + 8e00450 commit 50c0f35
Show file tree
Hide file tree
Showing 8 changed files with 6 additions and 6 deletions.
10 changes: 6 additions & 4 deletions website/docs/docs/cloud/about-cloud-develop-defer.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,13 @@ Both the dbt Cloud IDE and the dbt Cloud CLI enable users to natively defer to p

<Lightbox src src="/img/docs/reference/defer-diagram.png" width="50%" title="Use 'defer' to modify end-of-pipeline models by pointing to production models, instead of running everything upstream." />

By default, dbt follows these rules:
When using `--defer`, dbt Cloud will follow this order of execution for resolving the `{{ ref() }}` functions.

- dbt uses the production locations of parent models to resolve `{{ ref() }}` functions, based on metadata from the production environment.
- If a development version of a deferred model exists, dbt preferentially uses the development database location when resolving the reference.
- Passing the [`--favor-state`](/reference/node-selection/defer#favor-state) flag overrides the default behavior and _always_ resolve refs using production metadata, regardless of the presence of a development relation.
1. If a development version of a deferred relation exists, dbt preferentially uses the development database location when resolving the reference.
2. If a development version doesn't exist, dbt uses the staging locations of parent relations based on metadata from the staging environment.
3. If both a development and staging version doesn't exist, dbt uses the production locations of parent relations based on metadata from the production environment.

**Note:** Passing the `--favor-state` flag will always resolve refs using production metadata, regardless of the presence of a development relation, skipping step #1.

For a clean slate, it's a good practice to drop the development schema at the start and end of your development cycle.

Expand Down
2 changes: 0 additions & 2 deletions website/docs/guides/adapter-creation.md
Original file line number Diff line number Diff line change
Expand Up @@ -1345,8 +1345,6 @@ Breaking this down:
<Lightbox src="/img/adapter-guide/3-additional-resources.png" title="more resources"/>
- Implementation instructions:
<Lightbox src="/img/adapter-guide/4-installation.png" title="more installation"/>
- Future plans
<Lightbox src="/img/adapter-guide/5-coming-up.png" title="coming soon"/>
- Contributor recognition (if applicable)
<Lightbox src="/img/adapter-guide/6-thank-contribs.png" title="thank yous"/>

Expand Down
Binary file modified website/static/img/adapter-guide/0-full-release-notes.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified website/static/img/adapter-guide/1-announcement.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified website/static/img/adapter-guide/2-short-description.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified website/static/img/adapter-guide/3-additional-resources.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified website/static/img/adapter-guide/4-installation.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified website/static/img/adapter-guide/6-thank-contribs.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 50c0f35

Please sign in to comment.