[Core] 1.9 upgrade guide #6184
Merged
[Core] 1.9 upgrade guide #6184
+119
−2
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
jtcohen6
reviewed
Oct 1, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
runleonarun
commented
Oct 1, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
runleonarun
commented
Oct 1, 2024
|
|
||
| While this works for many use-cases, there’s a clear limitation with this approach: *Some datasets are just too big to fit into one query.* | ||
|
|
||
| Starting in Core 1.9, you can use the new microbatch strategy to optimize your largest datasets -- **process your event data in discrete periods with their own SQL queries, rather than all at once.** The benefits include: |
There was a problem hiding this comment.
Suggested change
| Starting in Core 1.9, you can use the new microbatch strategy to optimize your largest datasets -- **process your event data in discrete periods with their own SQL queries, rather than all at once.** The benefits include: | |
| Starting in Core 1.9, you can use the new [microbatch strategy](/docs/build/incremental-microbatch) to optimize your largest datasets -- **process your event data in discrete periods with their own SQL queries, rather than all at once.** The benefits include: |
runleonarun
commented
Oct 1, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
runleonarun
commented
Oct 1, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
graciegoheen
reviewed
Oct 2, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
graciegoheen
reviewed
Oct 2, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
runleonarun
commented
Oct 2, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
graciegoheen
approved these changes
Oct 3, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
graciegoheen
reviewed
Oct 3, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
graciegoheen
reviewed
Oct 3, 2024
website/docs/docs/dbt-versions/core-upgrade/06-upgrading-to-v1.9.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
….9.md Co-authored-by: Grace Goheen <53586774+graciegoheen@users.noreply.github.com>
dbeatty10
reviewed
Oct 4, 2024
| @@ -71,7 +71,6 @@ Read more about [Snapshots meta fields](/docs/build/snapshots#snapshot-meta-fiel | |||
| We’ve made improvements to `state:modified` behaviors to help reduce the risk of false positives and negatives. Read more about [the `state:modified` behavior flags](#managing-changes-to-legacy-behaviors) that leverage these improvements: | |||
|
|
|||
| - Added environment-aware enhancements for environments where the logic purposefully differs (for example, materializing as a table in `prod` but a `view` in dev). | |||
| - Models that use `var` or `env_var` in their definition are included in `state:modified` when their values change. | |||
| @@ -80,7 +79,6 @@ dbt Core v1.9 has a handful of new flags for [managing changes to legacy behavi | |||
| You can read more about each of these behavior changes in the following links: | |||
|
|
|||
| - (Introduced, disabled by default) [`state_modified_compare_more_unrendered_values`](/reference/global-configs/behavior-changes#behavior-change-flags). Set to `True` to start persisting unrendered_database and unrendered_schema configs during source parsing, and do comparison on unrendered values during `state:modified` checks. | |||
| - (Introduced, disabled by default) [`state_modified_compare_vars`](/reference/global-configs/behavior-changes#behavior-change-flags). Set to `True` if a model uses a `var` or `env_var` in its definition. dbt will be able to identify its lineage to include the model in `state:modified` because the var or env_var value has changed. | |||
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.
Closes #6159
What are you changing in this pull request and why?
First draft of upgrade guide. This is the most current content!
Checklist