Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[C++] Array subclass constructors must set ArrayData::null_count to 0 when there is no validity bitmap #25001

Closed
asfimport opened this issue May 19, 2020 · 3 comments
Closed

[C++] Array subclass constructors must set ArrayData::null_count to 0 when there is no validity bitmap #25001

asfimport opened this issue May 19, 2020 · 3 comments
Assignees
@wesm
Labels
Component: C++ Type: bug
Milestone
1.0.0

Comments

@asfimport
Copy link

Many type-specific array constructors incorrectly set the null count to unknown. It would be better to set it to 0

Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney / @wesm

PRs and other links:

Note: This issue was originally created as ARROW-8863. Please see the migration documentation for further details.
@asfimport
Copy link
Author

Wes McKinney / @wesm:
A bug was just reported that is caused by this. Looking

@asfimport
Copy link
Author

Wes McKinney / @wesm:
Actually ARROW-9143 has a different underlying cause

@asfimport
Copy link
Author

Antoine Pitrou / @pitrou:
Issue resolved by pull request 7450
#7450

@asfimport asfimport added this to the 1.0.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wesm wesm

Labels
Component: C++ Type: bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
2 participants
@wesm @asfimport