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
Right now, for some tasks, such as DR, we need to continuously export objects from one workspace into another. Some objects, such as jobs, clusters, notebooks, etc., could be renamed without changing their ID (job ID, cluster ID, workspace object ID, etc.), but right now, the resource name is often generated from the object name, leading to the creation of a new object and the destruction of the previous version, which can cause the loss of previous data (job run history, ...).
It would be useful to track a mapping of ID -> resource_name and when doing the next export, check if the resource name has changed without changing the ID, and generate moved blocks for such renames.
The text was updated successfully, but these errors were encountered:
Right now, for some tasks, such as DR, we need to continuously export objects from one workspace into another. Some objects, such as jobs, clusters, notebooks, etc., could be renamed without changing their ID (job ID, cluster ID, workspace object ID, etc.), but right now, the resource name is often generated from the object name, leading to the creation of a new object and the destruction of the previous version, which can cause the loss of previous data (job run history, ...).
It would be useful to track a mapping of
ID
->resource_name
and when doing the next export, check if the resource name has changed without changing the ID, and generate moved blocks for such renames.The text was updated successfully, but these errors were encountered: