[Delta] When checks schema for writing, Delta enforces not null on a Nested Field only when its parent is not null #4121
+66
−19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which Delta project/connector is this regarding?
Description
This PR corrects Delta's handling of nullable checks for nested fields when writing data.
For example, consider the schema:
Previously, Delta rejected NULL values for
foo
, even when it was marked as nullable. This was because a NULLfoo
would also makefoo.bar
NULL.With this change, Delta now enforces
foo.bar
as non-null only whenfoo
itself is non-null. As a result:How was this patch tested?
UT
Does this PR introduce any user-facing changes?
No