-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[C#] Union arrays don't account for offset and length #41140
Comments
CurtHagenlocher
pushed a commit
that referenced
this issue
Apr 12, 2024
### Rationale for this change See #41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: #41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
Issue resolved by pull request 41165 |
vibhatha
pushed a commit
to vibhatha/arrow
that referenced
this issue
Apr 15, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
tolleybot
pushed a commit
to tmct/arrow
that referenced
this issue
May 2, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
tolleybot
pushed a commit
to tmct/arrow
that referenced
this issue
May 4, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
Adding this to 16.1.0 as this seems to fix the tests issue locally for me: #41397 |
raulcd
pushed a commit
that referenced
this issue
May 8, 2024
### Rationale for this change See #41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: #41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
rok
pushed a commit
to tmct/arrow
that referenced
this issue
May 8, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
rok
pushed a commit
to tmct/arrow
that referenced
this issue
May 8, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
vibhatha
pushed a commit
to vibhatha/arrow
that referenced
this issue
May 25, 2024
…pache#41165) ### Rationale for this change See apache#41140. This makes a sliced union array behave as expected without having to manually account for the array offset unless accessing the underlying buffers. ### What changes are included in this PR? Accounts for the offset and length when getting type ids, value offsets and field arrays for sparse and dense union arrays. ### Are these changes tested? Yes, I've updated the union array tests to cover this. ### Are there any user-facing changes? Yes, this is a user facing bug fix. * GitHub Issue: apache#41140 Authored-by: Adam Reeve <[email protected]> Signed-off-by: Curt Hagenlocher <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
Similar to #40790, a sliced union array doesn't behave as expected as none of the methods or properties account for the offset and length.
This should work differently for sparse and dense unions. For a sparse union, the child arrays should be sliced when accessed, and the offset and slice should be accounted for in the
TypeIds
span. For a dense union, the child arrays shouldn't be sliced but theTypeIds
andValueOffsets
spans should.Component(s)
C#
The text was updated successfully, but these errors were encountered: