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.

Sign up for GitHub

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

Jump to bottom

New flag --defer-state for more-granular control of state used for deferral versus logic comparison #3696

Closed
1 task done
jtcohen6 opened this issue Jul 10, 2023 · 0 comments · Fixed by #3728
Closed
1 task done

New flag --defer-state for more-granular control of state used for deferral versus logic comparison #3696

jtcohen6 opened this issue Jul 10, 2023 · 0 comments · Fixed by #3728
Assignees
@jtcohen6
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear
Milestone
dbt Core v1.6 Doc...

Comments

@jtcohen6
Copy link
Collaborator

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/reference/node-selection/syntax#about-node-selection
https://docs.getdbt.com/reference/node-selection/defer

What part(s) of the page would you like to see updated?

Thorough context in the description of this issue:

Big idea is, you can now pass two manifests if you want to:

  • one for use in node selection, i.e. state:modified — this is --state, and roughly maps to "logical" state
  • one for use by --defer (and now clone) — this is --defer-state if specified, and roughly maps to "applied" state

In >90% of cases, we expect to resolve both using the same state/manifest.

(For context on what I mean by "logical" versus "applied" state: docs; internal notion)

Additional information
@jtcohen6 jtcohen6 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear idea Proposes an idea for new content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) labels Jul 10, 2023
@jtcohen6 jtcohen6 added this to the dbt Core v1.6 Documentation milestone Jul 10, 2023
@jtcohen6 jtcohen6 self-assigned this Jul 13, 2023
@jtcohen6 jtcohen6 mentioned this issue Jul 14, 2023
Merged
jtcohen6 added a commit that referenced this issue Jul 18, 2023
@jtcohen6
Revise v1.6 migration guide (#3728)
1991ca0 
resolves #3696
resolves #3723

Revise v1.6 migration guide for readability. Still a handful of TODOs.

### Materialized views
- Add `VersionBlock` components for adapter MVs, missed in
#3593
- We seem to be missing docs on Snowflake dynamic tables. I don't know
why #3494 was closed.

### Other updates
- Add manifest v10 (will need addition to schemas.getdbt.com:
dbt-labs/schemas.getdbt.com#24)
- Add note to upgrade guide for `state:old` and `state:unmodified`
(missed in #3596). I
haven't done a thorough comb-through of other closed v1.6 PRs to see
what needs addition to the migration guide.
@runleonarun runleonarun removed the idea Proposes an idea for new content label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jtcohen6 jtcohen6

Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear
Projects
None yet
Milestone
dbt Core v1.6 Documentation
Development

Successfully merging a pull request may close this issue.

Revise v1.6 migration guide dbt-labs/docs.getdbt.com
2 participants
@runleonarun @jtcohen6