You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing dbt-snowflake functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Not sure if this should be in the main dbt-core repository, but it would be really nice if when running the delete/insert it would check if temporary __dbt_tmp table had rows, and if not it would skip the insert/delete step.
This would not work well for views, as it might be expensive to operate on them.
Describe alternatives you've considered
Just living with it.
Who will this benefit?
Users of the incremental builds with Snowflake with large tables.
Are you interested in contributing this feature?
yes
Anything else?
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Feature] Don't run insert/delete for incremental models when no data has been changed
[ADAP-875] [Feature] Don't run insert/delete for incremental models when no data has been changed
Sep 7, 2023
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.
Is this your first time submitting a feature request?
Describe the feature
Not sure if this should be in the main dbt-core repository, but it would be really nice if when running the delete/insert it would check if temporary
__dbt_tmp
table had rows, and if not it would skip the insert/delete step.This would not work well for views, as it might be expensive to operate on them.
Describe alternatives you've considered
Just living with it.
Who will this benefit?
Users of the incremental builds with Snowflake with large tables.
Are you interested in contributing this feature?
yes
Anything else?
No response
The text was updated successfully, but these errors were encountered: