A

Wednesday, February 8th, 2023 5:16 PM

GCP Data Catalog Spring Boot integration

We are testing v2.2.2 of the Collibra and Google Data Catalog bi-directional integration.

We have not used either of the .CMA files from sbi-gcp-data-catalog-2.2.2\src\main\resources but have manually setup all required Assets, Attributes and Relations. We have amended the “CustomConstants.java” to use the object id’s for the custom assets.

We are able to ingest from GCP Data Catalog, however we receive an error when calling “https://localhost:8080/collibraToGcp

{
“message”: “Internal error during execution.”,
“exceptionMessage”: “{“message”:“There are one or more validation errors.”,“details”:“Status Code is 400 - Bad Request.\r\n\tDetailed Exception: {\r\n\t\tStatus Code: 400\r\n\t\tError Message: Incorrect ViewConfig: attributeNodeLabelNotFound - [2209ffe6-3163-4281-bee8-2127fc20b5c9]\r\n\t\tCollibra Error Type: Incorrect ViewConfig: attributeNodeLabelNotFound - [2209ffe6-3163-4281-bee8-2127fc20b5c9]\r\n\t}”}”
}

I am unable to find that attribute object_id 2209ffe6-3163-4281-bee8-2127fc20b5c9 in Collibra.
Are we missing a configuration step, or do both .CMA files need to be run in addition to the manual Metamodel setup?

Thanks,

Ade

3 Messages

2 years ago

Hello Ade,

I had faced this issue when I was playing around with this integration. I believe this is an issue with the id used in the latest 2.2.2 version for the attribute Remove Tag. In the previous versions, I believe this attribute was created with the id 205d88b8-2378-4ca3-8ed2-4cd39a8a41de

For me the /collibraToGcp started to work fine when I amended the id for the relatedRemoveTag value to 205d88b8-2378-4ca3-8ed2-4cd39a8a41de in the exportCollibraDataAttributesTvg.json and the exportCollibraDataAttributesTvgNoFilter.json files instead of the erroring id 2209ffe6-3163-4281-bee8-2127fc20b5c9

Hope this helps.

Kind Regards,
Abhi

8 Messages

2 years ago

Hi Abhi,

Thank you for taking the time to reply. I had arrived at the same conclusion as yourself, and have made that config change. The integration does run, but I cannot see it pushing any changes to GCP. Did you run the .CMA files in your environment?

Ade

3 Messages

No Ade.

I had manually created the custom Asset Types, Attributes, Relations and Assignments as per their initial version documentation (i.e. the 2.1.0 version). The ids used in that version and the ids in the v2.2.2 are different. Hence, these were breaking for me. When I changed these to the ids that were used in the v2.1.0, it worked for me.

Kind Regards,
Abhi

8 Messages

2 years ago

Looping in @spring-team.collibra.com for any further insight. Many thanks.

Loading...