perf: Optimize NULL handling in arrays_zip#21475
Merged
mbutrovich merged 2 commits intoapache:mainfrom Apr 10, 2026
Merged
Conversation
mbutrovich
approved these changes
Apr 10, 2026
Contributor
mbutrovich
left a comment
mbutrovich
left a comment
There was a problem hiding this comment.
Makes sense to me. Seems more idiomatic with Arrow-rs, and we'll take performance wins! Thanks @neilconway!
metegenez
reviewed
Apr 10, 2026
Contributor
metegenez
left a comment
metegenez
left a comment
There was a problem hiding this comment.
Could you add a 50% null density case to the benchmark? I am not sure we are firing the all-null-row early exit.
LGTM.
metegenez
approved these changes
Apr 10, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Which issue does this PR close?
arrays_zip#21474.Rationale for this change
arrays_zipwas building aVec<bool>and then converting it to aNullBuffer. It is simpler and (a bit) faster to just useNullBuffer/NullBufferBuilderdirectly.Benchmarks (ARM64):
The improvement is not massive but it's non-zero, and the resulting code is cleaner and more idiomatic.
What changes are included in this PR?
Are these changes tested?
Yes.
Are there any user-facing changes?
No.