feat(reader): null struct default values in create_column #1847
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.
Fixes
TestSparkReaderDeletes.testPosDeletesOnParquetFileWithMultipleRowGroupsin Iceberg Java 1.10 with DataFusion Comet.Which issue does this PR close?
What changes are included in this PR?
RecordBatchTransformerdoes not have exhaustive nested type support yet, this adds logic tocreate_columnin the specific scenario for a schema evolution with a new struct column that uses the default NULL value.Are these changes tested?
New test to reflect what happens with Iceberg Java 1.10's
TestSparkReaderDeletes.testPosDeletesOnParquetFileWithMultipleRowGroups. The test is misleading, since I figured testing positional deletes would just be a delete vector and be schema agnostic, but it includes schema change with binary and struct types so we need default NULL values.