Florian Eiden
Florian Eiden
Our current approach to decide if/how to solve these issues is: ### Can this problem be solved in user land? Is there a decent work around? Here it seems like...
Thanks for the update @vergenzt. Do you mind sharing why you pivoted away from external tables, and for what alternative? That is if it's not really specific to your own...
Hey there! I'm still trying to understand the scope of work here. Is the ask to add a [model config](https://docs.getdbt.com/reference/model-configs) applicable to table and incremental only, to indicate that `CREATE...
Hi @adammarples - can you please tell me more? The adapters where we support an `insert_overwrite` strategy for incremental, we do because the overwrite is done at the partition level....
@markproctor1 I think we agree here. There is value, but not limited to incremental models. So it's not an incremental strategy, but rather an overall switch to make all drop/replace...
I think I covered the fact that it was not a strategy for incremental models. Could it be a materialization by itself? Materializations are about the type of object being...
I agree! I don't think we should name it `insert_overwrite`, despite the DDL being `INSERT OVERWRITE` Maybe something like: ```SQL {{ config(materialized='table', overwrite=true) }} ``` After more thinking, maybe we...
Since you already have some code there, would you be interested in contributing a PR? I'll flag this issue as `help_wanted` if you do ;)
Like discussed, I would not be clever. If we limit the scope of `overwrite` to simple runs for `tables`, then `INSERT OVERWRITE` is an optimization that you should only use...