-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[Format] C Data Interface: clarify nullability of buffer pointers #14805
Comments
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Dec 1, 2022
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Dec 1, 2022
This was referenced Dec 7, 2022
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Jan 17, 2023
The C data interface may expose null data pointers for zero-sized buffers. Make sure that all buffer pointers remain non-null internally. Followup to apacheGH-14805.
This was referenced Jan 30, 2023
lidavidm
added a commit
that referenced
this issue
Jan 31, 2023
…33951) ### Rationale for this change While #14805 clarified that NULL buffers are valid in the C Data Interface, not all implementations handle this correctly (or were fixed, but earlier versions still exist). ### What changes are included in this PR? Export a non-NULL dummy buffer for nil/empty buffers to ensure compatibility. ### Are these changes tested? A regression test is included. * Closes: #33936 Authored-by: David Li <li.davidm96@gmail.com> Signed-off-by: David Li <li.davidm96@gmail.com>
sjperkins
pushed a commit
to sjperkins/arrow
that referenced
this issue
Feb 10, 2023
…ffers (apache#33951) ### Rationale for this change While apache#14805 clarified that NULL buffers are valid in the C Data Interface, not all implementations handle this correctly (or were fixed, but earlier versions still exist). ### What changes are included in this PR? Export a non-NULL dummy buffer for nil/empty buffers to ensure compatibility. ### Are these changes tested? A regression test is included. * Closes: apache#33936 Authored-by: David Li <li.davidm96@gmail.com> Signed-off-by: David Li <li.davidm96@gmail.com>
gringasalpastor
pushed a commit
to gringasalpastor/arrow
that referenced
this issue
Feb 17, 2023
…ffers (apache#33951) ### Rationale for this change While apache#14805 clarified that NULL buffers are valid in the C Data Interface, not all implementations handle this correctly (or were fixed, but earlier versions still exist). ### What changes are included in this PR? Export a non-NULL dummy buffer for nil/empty buffers to ensure compatibility. ### Are these changes tested? A regression test is included. * Closes: apache#33936 Authored-by: David Li <li.davidm96@gmail.com> Signed-off-by: David Li <li.davidm96@gmail.com>
fatemehp
pushed a commit
to fatemehp/arrow
that referenced
this issue
Feb 24, 2023
…ffers (apache#33951) ### Rationale for this change While apache#14805 clarified that NULL buffers are valid in the C Data Interface, not all implementations handle this correctly (or were fixed, but earlier versions still exist). ### What changes are included in this PR? Export a non-NULL dummy buffer for nil/empty buffers to ensure compatibility. ### Are these changes tested? A regression test is included. * Closes: apache#33936 Authored-by: David Li <li.davidm96@gmail.com> Signed-off-by: David Li <li.davidm96@gmail.com>
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.
In apache/arrow-nanoarrow#76 it was reported that some implementations may export zero-length buffers as a null pointer in the ArrowArray structure.
Given that this seems to be an accepted behavior in several implementations, we should probably make it explicitly legal in the C Data Interface spec.
Component(s)
Format
The text was updated successfully, but these errors were encountered: