39 Messages
How Refresh Conflict is working ?
Hi ,
I am using custom spring boot integration to ingest the metadata for report ,
for some of the report attribute i have description available inside my api repository, but for some report attribute i need to add description manually but i f i will run that integration again to refresh the metadata the manually added description will be lost , i found that Refresh Conflict is used to handle this type of scenario but i read the documentation and as per the documentation we can only use this on data sources .
is there any way we can use it for report attribute as well ?
Thanks,
Pratik
Community_Alex
683 Messages
•
15.3K Points
3 years ago
@spring-team.collibra.com, can someone possibly help @pratikkumar.b.mori.accenture.com with this issue?
0
0
springboot_team
368 Messages
3 years ago
Hello Pratik,
When using either the Spring Boot Integration Library or the Import API, the Refresh Conflict (https://productresources.collibra.com/docs/cloud-user/2021.01/#Catalog/RegisterDataSource/RefreshDataSource/co_resolve-refresh-conflicts.htm) is not supported out-of-the-box. It is supported when using Collibra Catalog.
As a side note, when using the Spring Boot Integration Library, it contains an option to mark old assets as obsolete (Documentation sub-section: “Marking Assets as Obsolete”). Additionally, for the Spring Boot integration not to override an attribute on the Collibra Platform, if possible, the attribute should not be defined as part of the upsert/import payload of the respective asset/s.
0
0