Ben Cassell
Ben Cassell
Please take a look at the lint failure; fix that and we're good to merge.
@dwreeves there have been a lot of changes (in fact, 2.0.latest is no longer being developed after my discussion with dbt labs today), so I'm going to try to replicate...
@dwreeves closing in favor of https://github.com/databricks/dbt-databricks/pull/661
@ValdarT do you have a proposal for how users would opt-in to this behavior?
Thanks for taking to the time to flesh out the proposal. If you need this feature soon, submitting a PR with an implementation will speed things up; otherwise know this...
This was initially not implemented due to issues I was having with materialized views and column comments; maybe this is no longer the case, and either way, I think it...
This is an interesting edge case that will require some significant testing. The safest change would be to only use alter in place of 'create or replace' if the table...
Alter for views is coming in 1.10.0. Its hard to recover from statement failure because the only place I can catch the exception is in python, outside of a materialization,...
Thanks for reporting. Need to rethink this.
@sundeep1687 you can skip optimize by setting DATABRICKS_SKIP_OPTIMIZE=true