-
Notifications
You must be signed in to change notification settings - Fork 784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix null_count computation in binary #3062
Conversation
|
||
let arg1: Int32Array = ArrayDataBuilder::new(DataType::Int32) | ||
.len(13) | ||
.null_count(13) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the test skip setting the null count explicitly and instead let the ArrayDataBuilder calculate it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems the parameter is actually ignored and build
always recalculates it. Only build_unchecked
would use it.
Looks good to me 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did a quick check that these are the only two places where we are using Buffer::count_set_bits in an incorrect way as this.
I've also filed #3067 to remove this particular footgun |
Benchmark runs are scheduled for baseline = 6b3a0a2 and contender = 6057cf7. 6057cf7 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Which issue does this PR close?
Closes #3061.
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?