22 Messages
•
405 Points
Best practice when Data Asset names change on a refresh?
What is the best practice to handle the situation of a data asset (Schema, Table, Column, etc) name changes on a refresh and the cataloged assets have human entered metadata and additional characteristics defined?
I know the existing cataloged asset has its status changed to “Missing from source” but how do we move the custom metadata provided by my stewards from the old (missing) assets to the newly cataloged assets? If this happens on a table with hundreds of columns what is the best way to migrate the information supplied by people to the newly cataloged stub records?
Thank you for helping us with this issue!
-Brian
fintanvan_ommen_kloeke
25 Messages
4 months ago
I am not sure there is a standard ‘best’ practice, but there are a couple of options I can think of:
In both cases I would see the bottle neck, and area of greatest risk, being the mapping of old name to new name.
0
0
brianlloyd
22 Messages
•
405 Points
4 months ago
Thank you for the information on this topic. I feel these options are potentially dangerous and can introduce errors in the transfer. I went ahead and added an Ideation DCC-I-2706 Automation to help migrate metadata when Data Asset names change,
Hopefully others will find this useful and Collibra can make a foundational capability to address this issue.
So go vote this one up!!
0
0