Skip to content

impl byte specefic version of inProgressArrays - #10799

Closed
Rich-T-kid wants to merge 1 commit into
apache:mainfrom
Rich-T-kid:rich-t-kid/byte-array-coalesce
Closed

impl byte specefic version of inProgressArrays#10799
Rich-T-kid wants to merge 1 commit into
apache:mainfrom
Rich-T-kid:rich-t-kid/byte-array-coalesce

Conversation

@Rich-T-kid

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@Rich-T-kid

Copy link
Copy Markdown
Contributor Author

will rebase after #10797 to run the benchmarks and open the PR for review if the benchmarks show good results

@Rich-T-kid

Copy link
Copy Markdown
Contributor Author

view comment #7764 (comment)

@Rich-T-kid Rich-T-kid closed this Aug 23, 2026
Jefffrey pushed a commit that referenced this pull request Aug 26, 2026
# 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.
-->

- works towards #7764.

# Rationale for this change
a way to measure progress in #7764 + #10799
<!--
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?
new benchmarks
<!--
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?
n/a
<!--
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)?

If this PR claims a performance improvement, please include evidence
such as benchmark results.
-->

# Are there any user-facing changes?
no
<!--
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.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arrow Changes to the arrow crate arrow-select

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[coalesce] Implement specialized BatchCoalescer::push_batch for StringArray

1 participant