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.

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

Add integration test case to explicitly check for optional validity buffer #17816

Closed
asfimport opened this issue Nov 15, 2017 · 1 comment
Closed

Comments

@asfimport
Copy link

When the null count of a Field is 0 the validity buffer is optional in a RecordBatch message. From ARROW-1476, integration tests were failing because of this (see discussion here #1316 (comment)). The failure occurred due to chance of the random seed for generating the validity buffer. We should explicitly test this case for integration testing in the future.

Reporter: Bryan Cutler / @BryanCutler
Assignee: Bryan Cutler / @BryanCutler

PRs and other links:

Note: This issue was originally created as ARROW-1821. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Wes McKinney / @wesm:
Issue resolved by pull request 1323
#1323

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants