[
https://issues.apache.org/jira/browse/FLINK-30721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30721:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> The confluent schema registry is not compatible with Apicurio schema registry
> -----------------------------------------------------------------------------
>
> Key: FLINK-30721
> URL: https://issues.apache.org/jira/browse/FLINK-30721
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Pedro Mázala
> Priority: Major
> Labels: pull-request-available, stale-major
>
> With the format `avro-confluent`, it is impossible to use
> [Apicurio|https://www.apicur.io/].
> [The
> code|https://github.com/apache/flink/blob/master/flink-formats/flink-avro-confluent-registry/src/main/java/org/apache/flink/formats/avro/registry/confluent/ConfluentSchemaRegistryCoder.java#L71]
> reads a 4-byte integer (see `readInt` documentation
> [here|https://docs.oracle.com/javase/7/docs/api/java/io/DataInput.html#readInt()])
> and Apicurio stores its schema ids as a long ([8
> bytes|https://docs.oracle.com/javase/7/docs/api/java/io/DataInput.html#readLong()]).
> The solution could be adding the schema size to be read from the log message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
