-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[CT-793] [Feature] Testable _tmp tables in incremental models #5427
Comments
Thanks @NiallRees! Two reasons I can see for wanting this:
I know folks have written (very tricky) custom materializations to accomplish both outcomes before. So long as the merge/upsert/overwrite logic is simple enough (and dbt really wants to keep it simple), there should be minimal or zero risk of the test passing on the "new" data (no dupes, no nulls, etc), and yet failing on the "final" table. Out of curiosity, have you experimented with using the |
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days. |
Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers. |
Hi Team, Any update on this feature? |
Is this your first time opening an issue?
Describe the Feature
Currently, it's only possible to apply dbt tests to the final table of an incremental model. There are circumstances where it would be useful to apply tests (both singular and generic) to the incremental _tmp table created by dbt in an incremental model. In large tables, it would drastically increase the speed and performance of tests by only tested new/updated data.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: