[SPARK-51637][PYTHON] Implement createColumnarReader for Python Data Source #50414
+188
−6
Conversation
This file contains 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
wengh
changed the title
|
@ueshin @HyukjinKwon @allisonwang-db Please take a look at this PR |
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.
What changes were proposed in this pull request?
This PR makes Python Data Sources read data in columnar batches rather than rows. Currently, data is already in columnar batches when passing from Python to JVM, but turned into rows in the
PartitionReaderFactory. This PR implementsPartitionReaderFactory.createColumnarReaderso that data remains in columnar format.Why are the changes needed?
To improve Python Data Source performance.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests and new test in
test_python_datasource.pyto check that nested arrays and structs are read correctly.Was this patch authored or co-authored using generative AI tooling?
No