majdyz opened a new pull request, #40929:
URL: https://github.com/apache/spark/pull/40929
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'core/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
This PR adds lazy allocation support for the backing array of ColumnVector
used in Spark VectorizedReader. This is added as a memory optimization for
addressing the memory utilization issue when reading a Parquet file with large
but sparse columns.
Out of scope of this PR:
- Lazy allocation support for `OffHeapColumnVector`.
### Why are the changes needed?
The scope of this change includes:
- Simplify `OnHeapColumnVector` to only use a single-byte array for various
data types.
- Introduced lazy loading to `data` array, e.g: allocating the array only on
first-write.
- Changed `nulls` byte array to use `BitSet` for a smaller memory footprint
and faster batch operations.
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description and/or an example to show the
behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Spark versions or within the unreleased branches such as master.
If no, write 'No'.
-->
No.
### How was this patch tested?
Existing tests:
* ColumnarBatchSuite
* ColumnVectorSuite
* ColumnVectorUtilsSuite
* ConstantColumnVectorSuite
Manual tests:
Tested on reading a Parquet file with a large nested struct with an array
with 16GB executors. This patch fixed the OutOfMemory exception.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
