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
This will allow users to easily modify the MERGE command to take into account additional data from the table_changes function (for example)
merge into {{ target }} as DBT_INTERNAL_DEST
using {{ source }} as DBT_INTERNAL_SOURCE
on {{ predicates | join(' and ') }}
when matched and DBT_INTERNAL_SOURCE._change_type = 'update_postimage' then update set {{ get_merge_update_set(update_columns, on_schema_change, source_columns) }}
when not matched and DBT_INTERNAL_SOURCE._change_type != 'delete' then insert {{ get_merge_insert(on_schema_change, source_columns) }}
when matched and DBT_INTERNAL_SOURCE._change_type = 'delete' then delete
The text was updated successfully, but these errors were encountered:
Looking at a similar issue reported here it seems this is the response when custom strategies aren't supported; dbt-databricks itself is called out in that response.
Another issue here is similar and that is talking about if there's not an adapter macro to get your custom strategy macro it will fail.
Describe the feature
Adding support for Custom Incremental Strategies.
Who will this benefit?
This will allow users to easily modify the MERGE command to take into account additional data from the table_changes function (for example)
The text was updated successfully, but these errors were encountered: