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
Just opening an issue to acknowledge this has not been supported yet.
Without field presence (default), missing fields from a message would be filled with their default value (e.g. 0 or '') rather than null. This used to be the common practice of protobuf.
However in some cases, it may be desired to use null for unset fields and only ingest 0/'' when the producer explicitly set them to this value.
This is related to optional and oneof in protobuf specification.
This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄
Just opening an issue to acknowledge this has not been supported yet.
Without field presence (default), missing fields from a message would be filled with their default value (e.g.
0
or''
) rather thannull
. This used to be the common practice of protobuf.However in some cases, it may be desired to use
null
for unset fields and only ingest0
/''
when the producer explicitly set them to this value.This is related to
optional
andoneof
in protobuf specification.https://protobuf.dev/programming-guides/field_presence/
The text was updated successfully, but these errors were encountered: