You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "sigalit (Jira)" <ji...@apache.org> on 2022/04/26 10:31:00 UTC
[jira] [Updated] (BEAM-14366) beam version 2.38 - upgrade apicurio-common-rest-client-common jar due to a critical bug
[ https://issues.apache.org/jira/browse/BEAM-14366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sigalit updated BEAM-14366:
---------------------------
Summary: beam version 2.38 - upgrade apicurio-common-rest-client-common jar due to a critical bug (was: beam version 2.38 uses)
> 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
>
> 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)