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.

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

Need to use --no-write-json to avoid empty STG_DBT__NODE_EXECUTIONS model #100

Closed
sfc-gh-dflippo opened this issue Mar 1, 2022 · 1 comment · Fixed by #108
Closed

Need to use --no-write-json to avoid empty STG_DBT__NODE_EXECUTIONS model #100

sfc-gh-dflippo opened this issue Mar 1, 2022 · 1 comment · Fixed by #108

Comments

@sfc-gh-dflippo
Copy link

Hello, recently I was tracking down why many of my models were empty and I tracked it down to the command I was using to invoke the new upload macro:
dbt run-operation upload_dbt_artifacts_v2

I found that my manifest.json was being replaced by the macro's execution and that was causing the STG_DBT__NODE_EXECUTIONS model to have zero rows because it has an inner join between stg_dbt__artifacts and stg_dbt__nodes. In my case the issue was resolved by using this command to upload instead:
dbt --no-write-json run-operation upload_dbt_artifacts_v2

I recommend the README.md be updated to include the --no-write-json parameter.

I also recommend committing the fix for issue #64 because that was also one of my root causes.

@NiallRees
Copy link
Contributor

Thanks for finding this @danflippo !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants