https://community.databricks.com/t5/get-started-discussions/blue-green-deployment-table-cloning-and-delta-live-table/m-p/46366#M1230 <P><SPAN>this a rather complex question that addresses Databricks users only. Let me recap a bit of the context that produced it. In the attempt to adopt the Blue/Green deployment protocol, we found good applications of the table cloning capabilities offered by Databricks. At every new deployment interaction, we clone the existing table into the new system while keeping the old one running. After the new system has been validated, we update the views so that anything works with no interruption. Well, but how do we "clone" the tables used in DLT pipelines? Any help or suggestion is appreciated!</SPAN></P> Wed, 27 Sep 2023 10:00:56 GMT 6502 2023-09-27T10:00:56Z https://community.databricks.com/t5/get-started-discussions/blue-green-deployment-table-cloning-and-delta-live-table/m-p/46366#M1230 <P><SPAN>this a rather complex question that addresses Databricks users only. Let me recap a bit of the context that produced it. In the attempt to adopt the Blue/Green deployment protocol, we found good applications of the table cloning capabilities offered by Databricks. At every new deployment interaction, we clone the existing table into the new system while keeping the old one running. After the new system has been validated, we update the views so that anything works with no interruption. Well, but how do we "clone" the tables used in DLT pipelines? Any help or suggestion is appreciated!</SPAN></P> Wed, 27 Sep 2023 10:00:56 GMT https://community.databricks.com/t5/get-started-discussions/blue-green-deployment-table-cloning-and-delta-live-table/m-p/46366#M1230 6502 2023-09-27T10:00:56Z