annik
Cc: Schwalbe Matthias ; user@flink.apache.org
Betreff: Re: Using pre-registered schemas with avro-confluent-registry format
is not possible
This comes up when the Schema Registry has authorization capabilities.
A producing application may not be authorized to call “register” when another
prin
n
> in the official release.
>
>
>
> *Von:* Meissner, Dylan
> *Gesendet:* Freitag, 30. Juni 2023 17:26
> *An:* Martijn Visser ; Schmeier, Jannik
>
> *Cc:* Schwalbe Matthias ;
> user@flink.apache.org
> *Betreff:* Re: Using pre-registered schemas with avro-confluent-registry
&g
Cc: Schwalbe Matthias , user@flink.apache.org
Subject: Re: Using pre-registered schemas with avro-confluent-registry format
is not possible
Caution: EXTERNAL EMAIL ALERT. This sender is not from your organization. If
you do not recognize the sender, DO NOT CLICK on links or attachments.
Hi
>
>
>
> Best regards,
>
> Jannik
>
>
>
>
>
> *Von:* Schwalbe Matthias
> *Gesendet:* Mittwoch, 31. Mai 2023 13:33
> *An:* Schmeier, Jannik ; user@flink.apache.org
> *Betreff:* RE: Using pre-registered schemas with avro-confluent-registry
> format is not p
Hi Jannik,
By default, Kafka client applications automatically register new schemas
[1]. You should be able to influence that by using properties, e.g. setting:
'properties.auto.register.schemas' = 'false'
'properties.use.latest.version' = 'true'
Best regards,
Martijn
[1]
https://docs.confluen
Hello Jannik,
Some things to consider (I had a similar problem a couple of years before):
* The schemaRegistryClient actually caches schema ids, so it will hit the
schema registry only once,
* The schema registered in schema registry needs to be byte-equal,
otherwise schema registry co
