[ 
https://issues.apache.org/jira/browse/BEAM-14366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sigalit updated BEAM-14366:
---------------------------
    Fix Version/s: Not applicable
       Resolution: Invalid
           Status: Resolved  (was: Triage Needed)

> beam version 2.38 - upgrade apicurio-common-rest-client-common jar due to a 
> critical bug
> ----------------------------------------------------------------------------------------
>
>                 Key: BEAM-14366
>                 URL: https://issues.apache.org/jira/browse/BEAM-14366
>             Project: Beam
>          Issue Type: Task
>          Components: beam-model
>            Reporter: sigalit
>            Priority: P1
>             Fix For: Not applicable
>
>
> pipeline implemented in beam and runs over flink uses apicurio as schema 
> registry.
> When increasing number of job parallelism we starting getting exceptions from 
> apicurio
> [https://github.com/Apicurio/apicurio-registry/issues/2132]
> The issue was fixed in apicurio-common-rest-client-common-0.1.8.Final.jar
> [https://github.com/Apicurio/apicurio-common-rest-client/commit/c6878993629a0fe2870979d810bd124bd3359aec]
> but BEAM is still using apicurio-common-rest-client-common-0.1.7.Final.jar
> when will it be possible to do the upgrade?
>  
> thanks



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to