libserdes not registering schema to schema registry when the schema is used for multiple topics

[nao921]

Looking to use the same schema as key for 2 Kafka topics, topicA and topicB. I'm using libserdes C++ client library to produce the records with Schema Registry setup.

When I produce for topicA for the first time, I observe that 2 new subjects are registered on Schema Registry as being topicA-key and topicB-value.

Using the same schema as key, after publishing an event onto topicB, topicB-key subject is nowhere to be found on Schema Registry, only topicB-value subject.

After some debug log printing, I see that libserdes checks in its local cache on the MD5 of a schema. If it is found in local cache, it will return the schema immediately and not register it with Schema Registry.

[passiondjc]

Hi,Could you please help me with this issue? i use below command to run example
./serdes-kafka-avro-client -P -b 10.202.8.11:40301 -t testschema -p 1 -r http://localhost:8081 -s testvertica -S '{"type":"record","name""testvertica","namespace":"test","fields":[{"name":"f1","type":"string"},{"name":"f2","type":"string"}]}'

enter:str: {"f1":"value2", "f2":"value3"}

./serdes-kafka-avro-client -C -b 10.202.8.11:40301 -t testschema -p 1 -r http://localhost:8081
show error message:
Failed to read avro value: Cannot read string value: Cannot read string length: Cannot read 1 bytes from memory bufferCannot read string value: Cannot read string length: Cannot read 1 bytes from memory buffer

[lukejackson]

Essentially the issue is that libserdes does not support the TopicNameStrategy, which is the default naming strategy in the Java Schema Registry client code. It only supports the RecordNameStrategy