-
Notifications
You must be signed in to change notification settings - Fork 995
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
Nfiann-manifest #6933
base: current
Are you sure you want to change the base?
Nfiann-manifest #6933
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
website/docs/reference/node-selection/state-comparison-caveats.md
Outdated
Show resolved
Hide resolved
website/docs/reference/node-selection/state-comparison-caveats.md
Outdated
Show resolved
Hide resolved
|
||
<Lightbox src="/img/docs/reference/saved-manifest-not-found.png" title="Saved manifest not found error" /> | ||
|
||
During the next run, the `target/manifest.json` is overwritten. Following this, it's read again to detect changes, but no changes are found. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what run?
|
||
#### Workaround | ||
|
||
- Move the manifest from the `target/` folder to a dedicated folder such as `state/` between step 2 of the run, and in step 4 of the run, use the command `mkdir state && mv target/manifest.json state/manifest.json`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i dont understand the steps referenced here? what's step 2, step 4?
|
||
Additionally, it's not recommended to set `--state` and `--target-path` to the same path while using state-dependent features like `--defer` and `state:modified` as it can lead to non-idempotent behavior, which may not work as expected. | ||
|
||
#### Workaround |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a workaround or are we saying 'to avoid having it overwritten'?
|
||
<Lightbox src="/img/docs/reference/saved-manifest-not-found.png" title="Saved manifest not found error" /> | ||
|
||
During the next run, the `target/manifest.json` is overwritten. Following this, it's read again to detect changes, but no changes are found. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is read again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hey Natalie, thanks for this! have a dded some questions/suggestions:
- clarification on what the steps in your referenced text
- shortening the title
- removing the word 'now'
- add this to the 1.5 migration guide. @jtcohen6 mentions we should add to the v1.5 migration guide, which is missing this pr.
- also should this content be added to the node selector methods doc as mentioned in the issue?
Co-authored-by: Mirna Wong <[email protected]>
What are you changing in this pull request and why?
I have created this PR raised by Jerco for this Git issue: #3482 to advise dbt overwrites the manifest.json file during parsing. If a user references --state information from the target/ directory, they may encounter a warning indicating that the saved manifest was not found, since the manifest.json is overwritten during parsing.
Closes: #3482
Checklist
🚀 Deployment available! Here are the direct links to the updated files: