Skip to content

v3.0.0

Compare
Choose a tag to compare
@Nevon Nevon released this 20 May 11:32
· 143 commits to master since this release
8efbdd6

This version is non-breaking for the overwhelming majority of users.

When creating an instance of SchemaRegistry for Protobuf without the messageName parameter confluent-schema-registry would, under certain circumstances, default to the wrong message type in the schema. Specifically, instead of defaulting to the first message type in the schema it would erroneously default to the first message type that did not define a nested type.

If you were relying on this behavior may need to either:

  • Start passing the messageName parameter instead of relying on the default behavior
  • Update your schemas and re-ingest messages accordingly

See issue #112 for more info

Added

  • Allow setting HTTP agent #108

Fixed

  • Fix default nested Protobuf type #113