1.0.0-beta.6 (2022-02-10)
Features Added
- The encoder APIs have been revamped to work on messages instead of buffers where the payload is the pure encoded-data. The schema ID became part of the content type of that message. This change will improve the experience of using this encoder with the other messaging clients (e.g. Event Hubs, Service Bus, and Event Grid clients). The encoder also supports decoding messages with payloads that follow the old format where the schema ID was part of the payload.
decodeMessageData
now supports decoding using a different but compatible schema
Breaking Changes
- The
SchemaRegistryAvroSerializer
class has been renamed toAvroEncoder
- The
serialize
method has been renamed toencodeMessageData
and it now returns a message - The
deserialize
method has been renamed todecodeMessageData
and it now takes a message as input
Other Changes
- The internal cache has been updated to be an LRU one with a max entries count of 128