-
Bug
-
Resolution: Done
-
Major
-
3.0.5.Final
-
None
This issue can appear if a field is first optional and later is marked required in the schema and a default value is assigned. When reading from a stream encoded with the first version of the schema we might not see the field and would expect the missing value to be replaced with the default. Default values do not work in this particular case.