[BUG] SchemaRegistryAvroSerializer Does Not Produce Same Avro as Javascript Serializer

[AsgerPilegaard]

Describe the bug
The java sdk SchemaRegistryAvroSerializer is not compatible with schemas uploaded by the javascript sdk SchemaRegistryHandler.

Main issue: The schema name, uploaded by the js SchemaRegistryHandler, does not contain the namespace only the name of the record.
Fact: The java SchemaRegistryAvroSerializer uses the full schema name from the local avro class to match with published schemas on the event hub schema registry.
Subsequent issue: The java SchemaRegistryAvroSerializer can not serialize/deserialize avro records using schemas published with js SchemaRegistryHandler.

Solution Idea:
Making the java sdk backward compatible with the js sdk would be the wrong solution, updating the js sdk would be the real fix.
As a minor flexibility fix, I suggest making the AvroSchemaRegistryUtils public and accessible in the SchemaRegistryAvroSerializerBuilder, enabling the caller to extend the AvroSchemaRegistryUtils class and overriding getSchemaName() method.

To Reproduce
Upload avro schemas using the js azure library "@azure/schema-registry": "^1.0.0-beta.1”.
Deserialize/serialize schemas using the java library “azure-data-schemaregistry-avro”: “1.0.0-beta.5”.

Code Snippet
String getSchemaName(Object object) {
return AvroSchemaUtils.getSchema(object).getFullName();
}

Expected behavior
AvroSchemaRegistryUtils should not be package private and accessible in the SchemaRegistryAvroSerializerBuilder.
The js SchemaRegistryHandler should upload schemas using the FullName (containing namespace).


[alzimmermsft]

Thank you for submitting this issue @AsgerPilegaard, would it be possible to also submit an issue against azure-sdk-for-js to track there as well.

[github-actions]

Hi @AsgerPilegaard, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.