Import API M:N relationships deleted
Hi all
Wanted to check if you noticed this behaviour of Import API (both normal import API as well as Synchronisation based Import API) in your Collibra environments -
Let us consider this sample data:
Table A contains
Column_1
Column_2
Column_3
Column_4
Table B contains
Column_4
Column_5
Column_6
Notice here - a column can be part of many tables (column_4) & a table can contain many columns.
If this data is imported in a single CSV file or JSON file, the import API is not importing all relations. Most of the times, it persists the last relationship for an asset.
The Core API persists all relations though.
Can you please confirm if it is the same at your end? Or, am I missing anything?
I raised a ticket with Collibra & heard back that “the Import API works as expected”.
sameary
·3 years ago · Edited@noor.shaik & @arthur.burkhardt There appears to be a possible solution for this problem now in the import API. See https://datacitizens.collibra.com/forum/t/import-api-relationsaction-query-parameter/2558 for a description of how to change “SET/REPLACE” to a “MERGE”
Alexandra Jorgenson
Admin4 years ago · Edited@noor.shaik @arthur.burkhardt One of you should add this ti the ideation portal (first search to see if it’s already there): “an attribute update rather than delete/create”. @ann.wuyts FYI.
arthurburkhardt
·4 years ago · Edited@noor.shaik Indeed, you’re expecting a “MERGE” strategy (upsert relations), but the import API strategy is “SET/REPLACE”.
Even if it could be even better to allow configuration of such strategies (I would LOVE an attribute update rather than delete/create), I think SET/REPLACE is better than nothing.