MultiFileReader: Fix for handling nested list/map default values #17589
Conversation
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
krlmlr
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Jun 2, 2025
MultiFileReader: Fix for handling nested list/map default values (duckdb/duckdb#17589)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up fixes from #17448
Nested default values were ignored, which caused this code not to correctly handle missing fields.
In addition, we can no longer directly emit the default value as the result since the default value is no longer equivalent to the actual value (e.g. the default value might be
{'list': {'k': NULL}}when the actual value should be[{'k': NULL}].) We fix this by allowingremap_structto takeNULLas remap target, in case there are zero columns used from the source struct.