Adds functionality to schema_registry_decode
to emit defaults or not
#2855
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This PR allows users to specify different behaviour for
schema_registry_decode
when decodingprotobuf
messages; allowing them to chose to Emit defaults.Why
if a protobuf message like
{"a": 0, "b": 1}
is encoded to protobuf, when we decode withschema_registry_decode
the resulting message is{"b": 1}
and the keyval"a": 0
is lost.This behaviour is controlled from
protojson.MarshalerOpts
with the fieldEmitDefaultValues
, which by fault isfalse
.