R

Thursday, January 5th, 2023 4:15 AM

Error when running gcp-dataflow-to-collibra-integration

I am using version 1.0.5 of “gcp-dataflow-to-collibra-integration” and version 1.1.5 of “collibra integation library” when running I get this error:

2023-01-04 22:08:50.100 [http-nio-4442-exec-2] ERROR com.collibra.marketplace.gcp.dataflow.exception.GlobalExceptionHandler - Internal error during execution.
com.collibra.marketplace.library.integration.exception.CollibraIntegrationLibraryException: {“message”:“An unexpected error occurred during execution.”,“details”:“Error reading entity from input stream.”,“cause”:“Unrecognized field “result” (class com.collibra.internal.api.model.output.Job), not marked as ignorable (17 known properties: “userId”, “createdOn”, “resourceType”, “endDate”, “name”, “system”, “startDate”, “state”, “visibility”, “cancelable”, “lastModifiedBy”, “type”, “id”, “lastModifiedOn”, “createdBy”, “progressPercentage”, “message”])\n at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 346] (through reference chain: com.collibra.internal.api.model.output.Job[“result”])”}
at com.collibra.marketplace.library.integration.CollibraExportApiHelper.exportAsCsv(CollibraExportApiHelper.java:163) ~[collibra-integration-library-1.1.5.jar:1.1.5]
at com.collibra.marketplace.library.integration.CollibraExportApiHelper.exportAsCsv(CollibraExportApiHelper.java:126) ~[collibra-integration-library-1.1.5.jar:1.1.5]
at com.collibra.marketplace.gcp.dataflow.service.ObsoleteAssetsService.getExistingAssetIdentifiers(ObsoleteAssetsService.java:88) ~[classes/:?]
at com.collibra.marketplace.gcp.dataflow.service.ObsoleteAssetsService.findObsoleteAssets(ObsoleteAssetsService.java:49) ~[classes/:?]
at com.collibra.marketplace.gcp.dataflow.BatchRequestProcessor.start(BatchRequestProcessor.java:147) ~[classes/:?]
at com.collibra.marketplace.gcp.dataflow.GCPSyncController.batchSyncRequest(GCPSyncController.java:40) ~[classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_345]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_345]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_345]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_345]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) ~[spring-web-5.3.18.jar:5.3.18]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:150) ~[spring-web-5.3.18.jar

Can someone help in resolving this error.

Thanks

-Rajesh Katarya

368 Messages

2 years ago

Hi @RajeshK,

Regarding the above error, this was addressed in a later version of the Integration Library.

Therefore, can you please try using a newer version of the Collibra Integration Library (e.g. v1.1.10 or v1.2.1)? Thanks

19 Messages

Hi,
Thanks for the quick response.
With 1.1.10 library there is a naming convention error with this application. Here is the error
2023-01-05 07:35:35.983 [main] ERROR org.springframework.boot.SpringApplication - Application run failed
org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [com.collibra.marketplace.gcp.dataflow.Application]; nested exception is org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name ‘collibraProperties’ for bean class [com.collibra.marketplace.library.integration.CollibraProperties] conflicts with existing, non-compatible bean definition of same name and class [com.collibra.marketplace.gcp.dataflow.config.CollibraProperties]
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:189) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:331) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:247) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:311) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:112) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:746) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:564) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:145) ~[spring-boot-2.5.12.jar:2.5.12]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) [spring-boot-2.5.12.jar:2.5.12]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:448) [spring-boot-2.5.12.jar:2.5.12]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:339) [spring-boot-2.5.12.jar:2.5.12]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1365) [spring-boot-2.5.12.jar:2.5.12]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1354) [spring-boot-2.5.12.jar:2.5.12]
at com.collibra.marketplace.gcp.dataflow.Application.main(Application.java:31) [classes/:?]
Caused by: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name ‘collibraProperties’ for bean class [com.collibra.marketplace.library.integration.CollibraProperties] conflicts with existing, non-compatible bean definition of same name and class [com.collibra.marketplace.gcp.dataflow.config.CollibraProperties]
at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:349) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:287) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:128) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:296) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:250) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:207) ~[spring-context-5.3.18.jar:5.3.18]
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:175) ~[spring-context-5.3.18.jar:5.3.18]

368 Messages

2 years ago

Hi @RajeshK,

Thanks for the update.

This was addressed in v1.0.6 of the GCP Dataflow to Collibra integration. Therefore, can you please try using the latest version?


(Note: there is a typo – “Version: 1.0.5” should be “Version: 1.0.6”. The actual version of the downloaded package is 1.0.6.)

Otherwise, can you please rename the class com.collibra.marketplace.gcp.dataflow.config.CollibraProperties to com.collibra.marketplace.gcp.dataflow.config.CollibraConfig? Thanks

Loading...