collibra-integration-library-sb3-1.0.1 no longer compatible with Workflow Definition API
Summary: The author reported compatibility issues with Collibra's latest integration library (version 1.0.1) for Spring Boot 3, which is incompatible with the Collibra Workflow Definition API after upgrading Collibra to version 2024.10. A deserialization exception was mentioned, alongside other API function concerns such as void return types limiting functionality. Another participant highlighted missing methods in the JobsApi. The author later noted that the issue with unknown enums was resolved in library version 1.1.2, but another user could not find this version publicly available.
Dear @springboot_team,
We've recently upgraded Collibra to 2024.10 and turns out that the latest integration library (1.0.1) for Spring Boot 3 is now longer compatible with Collibra Workflow Definition API.
When deploying the definition, API client throws an deserialization exception due to missing `Role` enum value:
Caused by: feign.FeignException: Cannot construct instance of `com.collibra.marketplace.library.generated.core.model.RoleImpl$PermissionsEnum`, problem: Unexpected value 'INSIGHTS_VIEW'
at[Source: (BufferedReader); line: 1, column: 2533](through reference chain: com.collibra.marketplace.library.generated.core.model.WorkflowDefinitionImpl["startRoles"]>java.util.ArrayList[0]>com.collibra.marketplace.library.generated.core.model.RoleImpl["permissions"]->java.util.ArrayList[14]) reading POSThttps://***.collibra.com/rest/2.0/workflowDefinitions
A quick workaround is to allow embedded object mapper to read unknown enum values:
Besides that I've noticed that the API class provides a `void` types for `getWorkflowDefinitionDiagram()` and `getWorkflowDefinitionXML()` methods, making them useless.
Are there any plans for library update?
marcinnowicki
OP1 year agoI confirm that the unknown enums issue has been solved with the latest integration library release (v.1.1.2)
Damien R
·1 year agoIs this version publicly available? I can't find it on Collibra's Marketplace.
Venkata Reddy Padala
·1 year ago · EditedWanted to join the wagon!
JobsApi is also missing FindJobsRequest to query for any jobs. It only has getJob and cancelJob. but we don't have method to query for any jobs, like get all running/ waiting jobs etc.
Also outputModuleApi fix would be great, (of course it was mentioned in documentation to use exportApiHelper but we don't want to spam the activities with export result for all the outputmodule exportJson query results.
Fixes to these 2 also would be great.
marcinnowicki
OP1 year ago · Edited@venkatareddy_padala I see that Collibra offers a separate package for Core API - it covers issues mentioned by us as you can see here: https://developer.collibra.com/apis/java/javav2/com/collibra/dgc/core/api/component/job/JobApi.html#findJobs(com.collibra.dgc.core.api.dto.job.FindJobsRequest)
I have no idea why Spring Boot library is not utilizing the core library as a dependency and provides its own, generated (and invalid) classes instead.