Describe the feature
At the moment, by default dbt clone allows dbt Databricks users to perform a SHALLOW clone in Databricks.
There's instances where a DEEP clone is needed, due to different demands from the users.
For example, you cannot SHALLOW clone a table that uses Auto Liquid Clustering, and then load the shallow clone with new data, it results in a database error.
My idea is to add a variable "clone_type" which takes the value "shallow" by default, but can be overwritten by the users
dbt clone --vars '{clone_type: deep}'
To allow the users to tell databricks to run a DEEP CLONE command instead of SHALLOW, for the models selected in the dbt command
Who will this benefit?
Anyone that have the need to DEEP clone objects in Databricks via dbt.
Are you interested in contributing this feature?
Yes, I can supply a draft version of the change.
Describe the feature
At the moment, by default dbt clone allows dbt Databricks users to perform a SHALLOW clone in Databricks.
There's instances where a DEEP clone is needed, due to different demands from the users.
For example, you cannot SHALLOW clone a table that uses Auto Liquid Clustering, and then load the shallow clone with new data, it results in a database error.
My idea is to add a variable "clone_type" which takes the value "shallow" by default, but can be overwritten by the users
dbt clone --vars '{clone_type: deep}'To allow the users to tell databricks to run a DEEP CLONE command instead of SHALLOW, for the models selected in the dbt command
Who will this benefit?
Anyone that have the need to DEEP clone objects in Databricks via dbt.
Are you interested in contributing this feature?
Yes, I can supply a draft version of the change.