Details
-
Task
-
Status: Resolved
-
P1
-
Resolution: Invalid
-
None
-
None
Description
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
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