Denodo Collibra Spring Boot Integration Build error

Question

Hello
I am trying to use the Denodo Collibra Spring boot Integration
When i try to build the POM, it shows multiple errors on various methods like below :-
“Method getCollibraCommunityName() is undefined for type Applicationconfig”
Here are the steps i have followed so far -

Installed Java 1.8
Installed Maven
Installed Collibra_Integration_Library jar in maven repository via command line
Imported the package as Maven project
When i try to build the above errors are showing up.
Any idea on this

springboot_team · Answer

Hello,

Just to let you know that v1.1.0 of the Denodo to Collibra integration containing the updated metamodel has been released on Collibra’s Marketplace.

Denodo to Collibra Integration - Collibra Marketplace

A Spring Boot integration that extracts metadata from Denodo, transforms it, and upserts it to the Collibra Platform.

springboot_team · Answer

Hello Simar, We had shared a pre-release version with you for testing through email. Can you please confirm whether this was received and whether you managed to test it? Thanks

springboot_team · Answer

Hello Simar ,

Thanks for the information provided.

To confirm, would having an attribute that indicates the cache type (e.g. full/partial/etc…) on the Table/View assets on Collibra, address this issue please? Thank you

@simarpal.singh.leaseplan.com

springboot_team · Answer

Hello Simar,

Thanks for the information provided.

It seems that the following IDs are not set correctly:

DENODOVIEW_COMPLEXRELATION_SOURCE (“00000000-0000-0000-0000-000000031007”);
DENODOVIEW_COMPLEXRELATION_TARGET (“00000000-0000-0000-0000-000000031007”);

To retrieve these IDs, from the Complex relations page, you should first enable the “Relation Ids” option:

Then, from the “Denodo View Relation” identify the source and target IDs:

Finally, set the CustomConstants enum values as follows:

DENODOVIEW_COMPLEXRELATION_SOURCE -> source relation ID
DENODOVIEW_COMPLEXRELATION_TARGET -> target relation ID

springboot_team · Answer

Hello Simar,

Thanks for your feedback.

Regarding the second point - lineage for cached objects - can you please provide more information into what is required?

Would this be the data that is returned by the GET_CACHE_TABLE and GET_CACHE_COLUMNS stored procedures please?

simarsingh · Answer

spring-team.collibra.com:

Yes, (currently) the Denodo integration will be updated to prepare a metamodel similar to the attached diagram which will include the Column-to-Column associations as Complex Relations.

Here are our questions on next version of integrator ?

Can we show lineage of objects between 2 databases in Denodo ?
2 . Currently we are not able to see lineage for Cache objects in denodo ? Can this be addressed ?

springboot_team · Answer

Hello Simar,

Thanks, currently the new version is being finalised and reviewed.

In case you have and feedback, please let us know.

Will update this post once this new version is published on Collibra’s Marketplace.

springboot_team · Answer

Hello Simar,

Thanks for the update.

Yes, (currently) the Denodo integration will be updated to prepare a metamodel similar to the attached diagram which will include the Column-to-Column associations as Complex Relations.

As can be seen from the attached image, each Column-to-Column complex relation will include the following attributes:

Multiplicity
Left Role Description
Right Role Description

Can you please advise whether this is as expected? Thank you

springboot_team · Answer

Hello Simar,

Thanks for the update.

Can you please try adding the following line to the com.collibra.marketplace.denodo.component.CollibraAssetTransformer class, line 108 (before the return statement) and then test the integration again? (A fix will be released soon)

complexRelationsToUpsert = complexRelationsToUpsert.stream().distinct().collect(Collectors.toList());

simarsingh · Answer

Hello Team,

We did the change.
Metadata from Denodo application is getting ingested but we did not see any complex relations and lineage for the assets ingested.
On investigating the Collibra logs we got multiple errors :-
Error 1 -
2022-04-04 12:24:26.715 [jobExecutor-5] ERROR c.c.d.c.io.job.OutputViewJobRunner - An error occurred during the export [session_hash=db8bf7bd3e43e9a31f281a1d0d0a7033, authenticated_id=8b22846f-0cbf-454a-ba1e-4f438a09f676, ehcache-txid=9776774, trace_id=a905fb41af17216be34c00c76ee0cd59, trace_flags=01, span_id=670fd1eb3bdf3f4a]
com.collibra.common.exception.CollibraIllegalArgumentException: fileResourceSizeTooSmall

Params: [exportb9d2fe38cece489b8bb35151d22aa961.csv]*
at com.collibra.dgc.core.service.file.impl.FileServiceImpl.checkFileSize(FileServiceImpl.java:541)*
at com.collibra.dgc.core.service.file.impl.FileServiceImpl.addFile(FileServiceImpl.java:202)*
at com.collibra.dgc.core.service.file.impl.FileServiceImpl.addFile(FileServiceImpl.java:185)*
at sun.reflect.GeneratedMethodAccessor5022.invoke(Unknown Source)*

Error 2
2022-04-04 12:27:26.651 [jobExecutor-5] ERROR c.c.d.i.c.j.AbstractImportJobRunner - Error during import. [session_hash=cf3b3063e79d9fcda6fbcf10cb6f381f, authenticated_id=8b22846f-0cbf-454a-ba1e-4f438a09f676, ehcache-txid=9784455, trace_id=66e8ececa260f6661dba4185f1dc4fb4, trace_flags=01, span_id=45d4323cd93a4a4f]
java.lang.IllegalStateException: Duplicate key [RelationIdentifier{source=AssetIdentifier{name=‘null’, domain=null, resourceType=‘CR’} AbstractMappingSupportingIdentifier{mapping=null} AbstractIdentifier{id=null}, type=RelationTypeIdentifier{direction=null} AbstractIdentifier{id=05b0855b-3727-4a6e-a30f-aee83eda35f8}, target=AssetIdentifier{name=‘null’, domain=null, resourceType=‘null’} AbstractMappingSupportingIdentifier{mapping=null} AbstractIdentifier{id=b3ce5f73-438e-4956-a594-5c0f5713007b}} AbstractIdentifier{id=null}, RelationIdentifier{source=AssetIdentifier{name=‘null’, domain=null, resourceType=‘CR’} AbstractMappingSupportingIdentifier{mapping=null} AbstractIdentifier{id=null}, type=RelationTypeIdentifier{direction=null} AbstractIdentifier{id=3948ecab-53ad-4b7f-826e-3347022f8e1d}, target=AssetIdentifier{name=‘null’, domain=null, resourceType=‘null’} AbstractMappingSupportingIdentifier{mapping=null} AbstractIdentifier{id=865c09df-fbe6-481a-b825-83619433b3e5}} AbstractIdentifier{id=null}]
at java.util.stream.Collectors.lambda$throwingMerger$0(Collectors.java:133)

Error 3 -
2022-04-04 12:30:08.276 [http-nio-0.0.0.0-4400-exec-6] ERROR c.c.c.r.e.NotFoundExceptionMapper - A web application exception has occurred [authenticated_id=94d8264d-40d3-402d-a037-3ce0e02f492a, session_hash=12c0019d1fb527a65f33ba5f5be6cadb, trace_id=d909c402a8ef47578cfea0d1f11e8ba8, trace_flags=01, span_id=3dda6190b5cbaac6]
javax.ws.rs.NotFoundException: HTTP 404 Not Found

springboot_team · Answer

Hello Simar,

Thanks for the information provided.

It seems that the following IDs are not set correctly:

DENODOVIEW_COMPLEXRELATION_SOURCE (“00000000-0000-0000-0000-000000031007”);
DENODOVIEW_COMPLEXRELATION_TARGET (“00000000-0000-0000-0000-000000031007”);

To retrieve these IDs, from the Complex relations page, you should first enable the “Relation Ids” option:

Then, from the “Denodo View Relation” identify the source and target IDs:

Finally, set the CustomConstants enum values as follows:

DENODOVIEW_COMPLEXRELATION_SOURCE -> source relation ID
DENODOVIEW_COMPLEXRELATION_TARGET -> target relation ID

simarsingh · Answer

We are able to see some assets ingested in Collibra.
But still received error on Relation does not exist.
Validated all the UUIDs and assignments.
Here is the snapshot of the code where we have defined the UUIDs -

public enum AttributeType implements CollibraAttributeTypeInterface {

DENODOVIEW_COMPLEXRELATION_DEPENDENCYTYPE(“Dependency Type”, “7e5abaa5-ccfd-4ef2-9d1f-f413507f220d”); // TODO: Set the Collibra Platform ID of the

DATABASE_CONTAINS_BIFOLDER (“1486d923-0e8e-498d-9b2a-4e9e0f881447”),

DENODOVIEW_COMPLEXRELATION_SOURCE (“00000000-0000-0000-0000-000000031007”),

DENODOVIEW_COMPLEXRELATION_TARGET (“00000000-0000-0000-0000-000000031007”);

DENODO_VIEW_RELATION (“Denodo View Relation”, “4afe0f8f-e039-42cc-8294-2ed2ac12a8d5”);

springboot_team · Answer

Hello Simar,

Regarding the following error, it seems that one of the relation types defined in the com.collibra.marketplace.denodo.util.CustomConstants class does not exist on the Collibra instance.

No relation type matches the specified criteria

Can you please confirm that the respective resource IDs exist on your Collibra instance?

springboot_team · Answer

Hello Simar, Thanks for the confirmation. Regarding the debug logs, yes, can you please set lines 26 and 30 to DEBUG?

springboot_team · Answer

Hello Simar, Thanks for the confirmation. Regarding the debug logs, yes, can you please set lines 26 and 30 to DEBUG?

springboot_team · Answer

Hello Simar,

Thanks for the update.

Regarding the configuration properties, can you please confirm whether any changes were made to the spring.datasource.* properties?

Can you please also confirm whether inside the src/main/resources folder there is a schema.sql file?

Additionally, can you please enable debug logging, trigger the integration, and then send the integration log file to [email protected]? Note: Please remove any sensitive/confidential information prior to doing so. Thank you

springboot_team · Answer

Hello Simar,

Regarding the exception message, since mock data is being used, can you please confirm whether any modifications were made to the integration downloaded from Collibra’s Marketplace? Thank you

springboot_team · Answer

Hello Simar,

Regarding the exception message, since mock data is being used, can you please confirm whether any modifications were made to the integration downloaded from Collibra’s Marketplace? Thank you

simarsingh · Answer

Team we tried with Postman attaching the configuration and error snapshot

springboot_team · Answer

Hello Simar,

Regarding the following error, the HTTP listening endpoint of the Denodo to Collibra integration listens for request having type POST instead of GET.

simarpal.singh.leaseplan.com:

HttpRequestMethodNotSupportedException: Request method ‘GET’ not supported

Amongst others, this could be achieved through Postman (https://www.postman.com/) or using the following cURL request (X-Use-Mock-Data -> when set to true, the mock data would be used):

curl --location --request POST 'https://<host>:<port>/sync?denodoDatabase=test' \
--header 'X-Use-Mock-Data: true' \
--header 'Authorization: Basic <encoded-credentials>'

simarsingh · Answer

Update ------
When we trigger the integration now and run the sync command , it logged below error -

2022-03-23 15:58:34,198 [http-nio-8442-exec-1] ERROR com.collibra.marketplace.denodo.exception.GlobalExceptionHandler - Internal error during execution.
org.springframework.web.HttpRequestMethodNotSupportedException: Request method ‘GET’ not supported
at org.springframework.web.servlet.mvc.method.RequestMappingInfoHandlerMapping.handleNoMatch(RequestMappingInfoHandlerMapping.java:253) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.lookupHandlerMethod(AbstractHandlerMethodMapping.java:438) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.handler.AbstractHandlerMethodMapping.getHandlerInternal(AbstractHandlerMethodMapping.java:379) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.mvc.method.RequestMappingInfoHandlerMapping.getHandlerInternal(RequestMappingInfoHandlerMapping.java:125) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.mvc.method.RequestMappingInfoHandlerMapping.getHandlerInternal(RequestMappingInfoHandlerMapping.java:67) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.handler.AbstractHandlerMapping.getHandler(AbstractHandlerMapping.java:498) ~[spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.DispatcherServlet.getHandler(DispatcherServlet.java:1258) [spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1040) [spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:963) [spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) [spring-webmvc-5.3.9.jar!/:5.3.9]
at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:898) [spring-webmvc-5.3.9.jar!/:5.3.9]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:655) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) [spring-webmvc-5.3.9.jar!/:5.3.9]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:764) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:228) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) [tomcat-embed-websocket-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:121) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:115) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:105) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:178) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:110) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:80) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:55) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:211) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:183) [spring-security-web-5.5.1.jar!/:5.5.1]
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:358) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:271) [spring-web-5.3.9.jar!/:5.3.9]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:100) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.web.filter.FormContentFilter.doFilterInternal(FormContentFilter.java:93) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.boot.actuate.metrics.web.servlet.WebMvcMetricsFilter.doFilterInternal(WebMvcMetricsFilter.java:96) [spring-boot-actuator-2.5.3.jar!/:2.5.3]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) [spring-web-5.3.9.jar!/:5.3.9]
at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:119) [spring-web-5.3.9.jar!/:5.3.9]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:190) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:163) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:542) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:357) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:382) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:893) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1723) [tomcat-embed-core-9.0.50.jar!/:?]
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-9.0.50.jar!/:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_312]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_312]
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-9.0.50.jar!/:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312]

arthurburkhardt · Answer

What makes you think anything has completed successfully? I cannot find any such message in your logs.

arthurburkhardt · Answer

What makes you think anything has completed successfully? I cannot find any such message in your logs.

simarsingh · Answer

We disabled SSL
We were able to successfully deploy the integration.
Here are the logs working_logs_deployment.txt (11.5 KB)

Now we are trying to use this integration as Linux service by creating .service file.
But we are getting the below logs and no metadata is getting ingested.error_logs_description.txt (46.0 KB)
Can you please help us ?

springboot_team · Answer

Hello Simar,

Sure, as specified in the Denodo to Collibra documentation, these properties are used to define the basic authentication credentials that is enabled on the HTTP listening endpoint used to trigger the integration.

Therefore, these properties should be set to a custom username and a strong password. Additionally, for security purposes, these can be encrypted as specified in section “Encrypt Configuration Properties” of the Denodo documentation.

springboot_team · Answer

Hello Simar,

Regarding this error, can you please confirm that the following properties were set (i.e. not empty) in the application.properties file? Thank you

trigger.api.username
trigger.api.password

springboot_team · Answer

Hello Simar,

Regarding this error, can you please confirm that the following properties were set (i.e. not empty) in the application.properties file? Thank you

trigger.api.username
trigger.api.password

springboot_team · Answer

Hello Simar,

Just to let you know that the updated version of the Spring Boot Integration Library, having version 1.1.4, has been released and is available on Collibra’s Marketplace.

Spring Boot Integration Library - Collibra Marketplace

Java classes to facilitate access to Collibra APIs.

springboot_team · Answer

Hello Simar,

Just to let you know that the updated version of the Spring Boot Integration Library, having version 1.1.4, has been released and is available on Collibra’s Marketplace.

Spring Boot Integration Library - Collibra Marketplace

Java classes to facilitate access to Collibra APIs.

springboot_team · Answer

Hello Simar,

Can you please check whether you Collibra instance has build number 20220302161146?

If it is the case, it is due to the REST API login request not returning the CSRF token (more details here).
To address this, a new version of the Spring Boot Integration Library should be released this week. Thank you

springboot_team · Answer

Hello Simar,

Can you please check whether you Collibra instance has build number 20220302161146?

If it is the case, it is due to the REST API login request not returning the CSRF token (more details here).
To address this, a new version of the Spring Boot Integration Library should be released this week. Thank you

springboot_team · Answer

Hello Simar,

Regarding the following error, it seems that one of the relation types defined in the com.collibra.marketplace.denodo.util.CustomConstants class does not exist on the Collibra instance.

No relation type matches the specified criteria

Can you please confirm that the respective resource IDs exist on your Collibra instance?

springboot_team · Answer

Hello Simar,

Regarding the following error, it seems that one of the relation types defined in the com.collibra.marketplace.denodo.util.CustomConstants class does not exist on the Collibra instance.

No relation type matches the specified criteria

Can you please confirm that the respective resource IDs exist on your Collibra instance?

springboot_team · Answer

Hello Simar,

Thanks for the update.

Regarding the error being encountered, can you please provide more details / the full error message or stack trace?

Additionally, can you please confirm that the following Spring Boot Integration Library was installed using the specified Maven command where the integration is being deployed/run?

Spring Boot Integration Library - Collibra Marketplace

Java classes to facilitate access to Collibra APIs.

springboot_team · Answer

Hello Simar,

Thanks for the update.

Regarding the error being encountered, can you please provide more details / the full error message or stack trace?

Additionally, can you please confirm that the following Spring Boot Integration Library was installed using the specified Maven command where the integration is being deployed/run?

Spring Boot Integration Library - Collibra Marketplace

Java classes to facilitate access to Collibra APIs.

springboot_team · Answer

Hello everyone,

Thanks for trying the Denodo to Collibra integration.

Regarding the missing getter methods when using Eclipse IDE, it could be due to Lombok which is not provided as part of the Eclipse IDE. (More information regarding Lombok can be found here.)

Therefore, can you please try downloading the latest version from here and then follow the steps explained in this page?

Thank you

springboot_team · Answer

Hello everyone,

Thanks for trying the Denodo to Collibra integration.

Regarding the missing getter methods when using Eclipse IDE, it could be due to Lombok which is not provided as part of the Eclipse IDE. (More information regarding Lombok can be found here.)

Therefore, can you please try downloading the latest version from here and then follow the steps explained in this page?

Thank you

arthurburkhardt · Answer

Yes, I agree with you. I’m quite puzzled with the integrations as they are today, and I’m very much waiting for the webinar on feb 24th to clarify the integration roadmap.

I saw some very good examples of custom integration frameworks, such as the Sinequa search engine.
There is a default template to follow:

xml to define the form in the main application to fill in the configuration
C# code to script the business logic of the integration

The result is a seamless integration into the application. Example here: plugins/SlackConnector at master · sinequa/plugins (github.com)

arthurburkhardt · Answer

simarpal.singh.leaseplan.com:

getCollibraCommunityName

Have you correctly defined the properties in the application.properties file?
Specifically this bit here:

# Names of the 'community' and 'domain' in the collibra instance where the metadata will be imported.
collibra.domain=
collibra.community=

If those properties are left empty, that might explain the error. They should be filled like:

# Names of the 'community' and 'domain' in the collibra instance where the metadata will be imported.
collibra.domain=Spring boot
collibra.community=Schemas

There are many more properties you need to define.

Koen Balm · Answer

Hi all! Any suggestions here? I’m facing exactly the same issue and even Collibra support pointed me to this forum… Thanks in advance, Koen

arthurburkhardt · Answer

Which command did you use to import the integration library into Maven?

1	Grant Rollerson SUNCORP CORPORATE SERVICES PTY LTD
2	Tom Friesen Algonquin College
3	SB S Benson Plus3 IT
4	S stefan_busch
5	Brian Lloyd USA TODAY Co.
6	D daverichard