Repository navigation
fix: fill schema-added nested columns with typed NULL arrays on read #2635
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
laskoviymishka
merged 7 commits into
apache:main
from
viirya:fix/2618-null-fill-nested-columns
Oct 6, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
31b5186
fix: fill schema-added nested columns with typed NULL arrays on read
viirya e845ae0
test(arrow): restructure #2618 nested-null test; trim comments
viirya cc794c8
Merge upstream main and address nested null-fill review feedback
viirya fbc8f72
Merge upstream main and reject unsupported complex initial defaults
viirya 47b82ae
Merge upstream main and resolve null-fill conflicts
viirya a8d823a
test: cover typed null helpers and clarify struct default support
viirya 6c79fc7
test: compare full evolved schema and link default follow-up
viirya File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sis added here with noinitial_default, so null-fill is exactly right. The case this PR quietly makes reachable is a struct added with a non-primitiveinitial_default(e.g.{}) — theand_thenin the transformer drops it toNone, so we'd null-fill instead of materializing the spec-mandated non-null struct. Not blocking, but a small pin-test here (even#[ignore]'d) documenting that gap would pair well with the follow-up I noted in the summary.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed — the extraction currently drops non-primitive defaults to
None. Added a TODO at thatand_thento keep the gap visible. I'd keep the regression test with the complex-default implementation in a follow-up, where we can cover the non-null struct and child-default semantics together.