Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
2.18.0
-
None
Description
Fix the nullability issues with protobuf to schema mapping
- Proto3 primitive types should be not nullable.
- Proto2 required types should be not nullable.
- Proto2 optional should also be not nullable as having an optional value doesn't mean it has not value. The spec states it has the optional value.
- Arrays should be not nullable, as proto arrays always have an empty array when no value is set.
- Maps should be not nullable, as proto maps always have an empty map when no value is set.
- Elements in an array should be not nullable, as nulls are not allowed in an array.
- Names and Values should be not nullable, as nulls are not allowed.
- Rows are nullable, as messages are nullable.
Attachments
Issue Links
- links to
