Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.3.0
-
None
-
None
Description
If a nested field has nullable entries a user shouldn't have to specify all of the fields, instead the nullable fields can have the default value of null. This will allow for more effective schema migration. We might want to put this behind a feature flag though.
Attachments
Issue Links
- is related to
-
SPARK-34378 Loosen AvroSerializer validation to allow extra nullable user-provided fields
- Resolved