fix: Properly set nested nullability when converting to pyarrow #217
+103
−13
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.
Schema.to_pyarrow_schema()was not preserving nullability constraints for nested column types. Inner fields were always marked nullable regardless of theirnullableparameter.Changes
pa.struct([fields])instead ofpa.struct({name: dtype})to preserve per-field nullabilitypa.large_list(field)instead ofpa.large_list(dtype)to preserve inner type nullability_pyarrow_dtype_of_shape()to usepa.list_(field, size)at the base case to preserve inner type nullability_nullable()helper and added tests for nested nullability preservationExample
Original prompt
Schema.to_pyarrow_schema(cls)ignores nested nullability #214💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.