-
Notifications
You must be signed in to change notification settings - Fork 975
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.
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
Update the 1.7 migration guide #4123
Comments
Hi Grace, when you do this, do you mind linking to dbt-labs/dbt-core#8307? as we have done in previous upgrade guides? Something like the below?
|
For consumers of dbt artifacts (metadata)The manifest schema version has been updated to v11. Specific changes:
@dbeatty10 do you know what the manifest schema changes were? The PR that bumped the version didn't seem to make any other changes. The run_results schema version has been updated to v5. Specific changes:
The nodes dictionary in the |
New and changed documentationdbt docs generate now supports
|
Outstanding:
|
Behavior change: Full information here -> dbt-labs/dbt-core#8704 (comment) Previously -> "the loaded_at_field is required to calculate freshness for a table. If a loaded_at_field is not provided, then dbt will not calculate freshness for the table." In 1.7 -> when you add a freshness: config to a source (and no loaded_at_field is provided), we will calculate freshness for that source via warehouse metadata tables when the warehouse supports it |
@graciegoheen here's a 1.7 adapter upgrade guide snippet about dbt show. My brain feels as though it's something worth calling out in the end user 1.7 guide, but perhaps not because this change just happened for all users of 1.5 and 1.6 as well? Do we this new behavior called out? Ok for the answer to be no, provided that we only ever rever to the new behavior. That said, I don't see any reference in the doc for dbt show that mentions this new behavior |
@dataders I just opened an issue for this here: #4256 I don't know the way you want to update the docs for |
## What are you changing in this pull request and why? addresses issue #4123 ## Checklist - [x] Review the [Content style guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md) and [About versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version) so my content adheres to these guidelines. - [x] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
Contributions
Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/guides/migration/versions/upgrading-to-v1.7
What part(s) of the page would you like to see updated?
We need to update this for what's going to be released in 1.7
Additional information
@graciegoheen -> to add what content needs to go onto this page
The text was updated successfully, but these errors were encountered: