feat: Allow LargeUTF8 -> String and LargeBinary -> Binary in arrow conversion #1294
+14
−0
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.
What changes are proposed in this pull request?
This PR relaxes type-checking rules to allow
LargeUtf8conversion toSTRINGandLargeBinaryconversion toBINARY. With this PR Delta kernel will allow committing arrow record batches that useLargeUtf8or that are built usingLargeStringBuilderor corresponding types for buildingLargeBinary.The main limitation that non-large variations of string and binary types impose is that they can hold up to 2 GBs of data, which makes it impossible to do kernel commits if there is a string or binary column larger than 2 GB. With this PR clients can just pass
RecordBatchthat usesLargeUtf8orLargeBinaryas column types.How was this change tested?
New UT