We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ArrayDataBuilder allows the user to specify a null count, alternatively calculating it if it is not set.
The problem is that the user-specified null count is never validated against the actual count of the buffer.
I suggest removing the ability to specify a null-count, and instead always calculating it.
Reporter: Neville Dipale / @nevi-me Assignee: Neville Dipale / @nevi-me
Note: This issue was originally created as ARROW-11063. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered:
Andrew Lamb / @alamb: Issue resolved by pull request 9041 #9041
Sorry, something went wrong.
nevi-me
No branches or pull requests
ArrayDataBuilder allows the user to specify a null count, alternatively calculating it if it is not set.
The problem is that the user-specified null count is never validated against the actual count of the buffer.
I suggest removing the ability to specify a null-count, and instead always calculating it.
Reporter: Neville Dipale / @nevi-me
Assignee: Neville Dipale / @nevi-me
PRs and other links:
Note: This issue was originally created as ARROW-11063. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: