[
https://issues.apache.org/jira/browse/FLINK-33045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885284#comment-17885284
]
nicolas paris commented on FLINK-33045:
---------------------------------------
attempt to fix this one. Tested with the datastream api w/ success. Not tested
table api. Feebacks are welcome
https://github.com/apache/flink/pull/25410
> format avro-confluent - disable auto-registering schema in registry
> -------------------------------------------------------------------
>
> Key: FLINK-33045
> URL: https://issues.apache.org/jira/browse/FLINK-33045
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.17.1
> Environment: Flink-Kubernetes-Operator
> format avro-confluent
> Reporter: Michael Lorenzi
> Priority: Minor
> Labels: pull-request-available
>
> {code:java}
> 'value.format' = 'avro-confluent',
> 'value.avro-confluent.url' = '<url>',
> 'value.avro-confluent.schema' = '<schema>', -- available in 1.18.x{code}
> Currently the format {{avro-confluent}} seems to always try to register the
> schema to the schema-registry, be it computed out of the table-schema or set
> by property {{schema}} (if 1.18.x is used).
> In our setup we would like to prevent our flink-jobs from registering
> schemas. Flink should only lookup the schema-id by calling {{getId}} from
> confluents schema-registry-client. We control publishing of new
> schema-versions outside of flink.
> The bevaviour is expected to be similar to the behvaiour of
> KafkaAvroSerializer from confluent when {{auto.register.schemas=false}} is
> set.
> Could there be a option like
> {code:java}
> 'value.avro-confluent.auto.register.schema' = 'false'{code}
> to disable auto-registering schema to the schema-registry?
> Thank you for your help!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
