[AVRO-1927] If a default value is set, Avro allows null values in non-nullable fields.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.8.1
• Component/s: java
• Assignee: Unassigned
• Reporter: Andreas Maier
• Created: 23/Sep/16 14:05
• Updated: 21/Jul/19 05:17

Description

With an avro schema like

{
  "name": "myfield",
  "type": "string",
  "default": ""
}

the following code should throw an exception

MyObject myObject = MyObject.newBuilder().setMyfield(null).build();

But instead the value of myfield is set to null, which causes an exception later when serializing myObject, because null is not a valid value for myfield.

I believe in this case setMyfield(null) should throw an exception, independent of the value of default.
See also
https://stackoverflow.com/questions/38509279/generated-avro-builder-set-null-doesnt-overwrite-with-default

Issue Links

• is superceded by: AVRO-2478 RecordBuilderBase.validate doesn't check nullability of composite types
• relates to: AVRO-1803 nullable fields and it's default value