Incremental metadata ingestion via APIs

Hello all,

We plan to do for a data source an initial/full metadata load into Collibra. Then, do incremental load at the desired frequency. For full load, we used import APIs. For incremental load, we plan to use Core APIs.

The data source metadata for both full load & incremental load (inserts, updates, deletes) is supplied through CSV files.

I notice the PUT commands for attributes, relations, responsibilities require an asset id.

Is there an out of the box template/APIs code for achieving this typical functionality? Appreciate.

noor

Posted 4 years ago · Edited 1 year ago·Last reply 4 years ago

1 comment

arthurburkhardt

·4 years ago · Edited

All rest APIs have a “Try it out” feature. You can just use that to get the corresponding curl command.

curl -X PATCH "https://xxx.collibra.com/rest/2.0/assets/00000000-0000-0000-0000-000000000000" -H "accept: application/json" -H "Content-Type: application/json" -d "{\"id\":\"3fa85f64-5717-4562-b3fc-2c963f66afa6\",\"name\":\"string\",\"displayName\":\"string\",\"typeId\":\"3fa85f64-5717-4562-b3fc-2c963f66afa6\",\"statusId\":\"3fa85f64-5717-4562-b3fc-2c963f66afa6\",\"domainId\":\"3fa85f64-5717-4562-b3fc-2c963f66afa6\",\"excludedFromAutoHyperlinking\":true}"

In the past, “PATCH” commands: had to be “POST” and override with “PATCH”
I don’t know if that holds true anymore.