[
https://issues.apache.org/jira/browse/FLINK-23160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Paul updated FLINK-23160:
--------------------------------
Affects Version/s: 1.14.0
> upgrade kafka-schema-registry-client to 6.1.2 for
> Flink-avro-confluent-registry
> -------------------------------------------------------------------------------
>
> Key: FLINK-23160
> URL: https://issues.apache.org/jira/browse/FLINK-23160
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.14.0, 1.13.1
> Reporter: Lian Jiang
> Priority: Major
>
> I am using ConfluentRegistryAvroSerializationSchema and blocked by a bug
> mentioned by [https://github.com/confluentinc/schema-registry/issues/1352]
> and the final fix is done by
> [https://github.com/confluentinc/schema-registry/pull/1839]. I did not find
> any easy workaround.
>
> Flink-avro-confluent-registry
> ([https://mvnrepository.com/artifact/org.apache.flink/flink-avro-confluent-registry])
> still use 5.5.2
> [kafka-schema-registry-client|https://mvnrepository.com/artifact/io.confluent/kafka-schema-registry-client]
> which does not have this fix. Could the next Flink upgrade this dependency
> to 6.1.2 which has the fix? Meanwhile, does the Flink community have any
> recommended workaround before dependency upgrade? Thanks for any help!
>
> From Fabian -
>
> Hi,
> Thanks for bringing this up. It looks to me like something we definitely want
> to fix. Unfortunately, I also do not see an easy workaround
> besides building your own flink-avro-confluent-registry and bumping the
> dependency.
> Can you create a JIRA ticket for bumping the dependencies and would you be
> willing to work on this? A few things are still a bit unclear
> i.e. are the newer confluent schema registry versions compatible with out
> Kafka version (2.4.1).
> Best,
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
