ClSlaid opened a new pull request, #9743:
URL: https://github.com/apache/arrow-rs/pull/9743

   When CachedArrayReader builds output from multiple cached batches, the old 
path materialized filtered byte arrays and then concatenated them. Replace that 
path for Utf8/Binary arrays with a direct coalescer that builds offsets, 
values, and validity in one output array, while keeping the existing generic 
MutableArrayData path for other types.
   
   Add a dedicated CachedArrayReader benchmark and a sparse string regression 
test so this path is measured directly and covered independently of broader 
parquet reader benchmarks.
   
   Benchmark vs main:
   - cached_array_reader/utf8_sparse_cross_batch_4m_rows/consume_batch: 11.949 
ms -> 4.153 ms (-65.2%)
   - arrow_reader_clickbench/sync/Q24 (same filter/projection as ClickBench 
Q26): 28.377 ms -> 28.443 ms (+0.2%, no measurable change)
   
   # Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax.
   -->
   
   - Closes #9060.
   
   # Rationale for this change
   
   <!--
   Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
   Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.
   -->
   
   # What changes are included in this PR?
   
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   
   # Are these changes tested?
   
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   # Are there any user-facing changes?
   
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   
   If there are any breaking changes to public APIs, please call them out.
   -->
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to