You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the Avro schema registry isn't supported, and I'd like to contribute to build in that support.
The first part of this would be to pass the topic/path name to the message serializer, as this is required by the Avro serializer to send to the schema registry.
I'll contribute a PR for this shortly.
The text was updated successfully, but these errors were encountered:
Perhaps if you could approach the path/topic passing to the serializer by having an additional serialization interface to be implemented similar to the one I did for SQS
#region Implementation of IMessageSerializer<string>
The SQS provider expected a string in the payload, so instead of serializing to byte[] the transport prefer the specialized string interface if one exists on the chosen serializer.
Of course, if we need to pass the path, and are forced to introduce a breaking change to IMessageSerializer, then it will be okay too.
I noticed that the Avro schema registry isn't supported, and I'd like to contribute to build in that support.
The first part of this would be to pass the topic/path name to the message serializer, as this is required by the Avro serializer to send to the schema registry.
I'll contribute a PR for this shortly.
The text was updated successfully, but these errors were encountered: