You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Joris Van den Bossche (Jira)" <ji...@apache.org> on 2019/11/06 13:08:00 UTC
[jira] [Commented] (ARROW-7071) [Python] Add Array convenience
method to create "masked" view with different validity bitmap
[ https://issues.apache.org/jira/browse/ARROW-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16968345#comment-16968345 ]
Joris Van den Bossche commented on ARROW-7071:
----------------------------------------------
> NB: I'm not sure what kind of pitfalls there might be if replacing an existing validity bitmap and exposing some previously-null values
I would say this is the responsibility of the user then?
What could happen? Are there potentially cases where interpreting the memory of a previously-null value as a value leads to segfaults? Like if you would do:
{code}
In [62]: a = pa.array([1, None, 3])
In [63]: np.frombuffer(a.buffers()[1], dtype="int64")
Out[63]: array([1, 0, 3])
{code}
> [Python] Add Array convenience method to create "masked" view with different validity bitmap
> --------------------------------------------------------------------------------------------
>
> Key: ARROW-7071
> URL: https://issues.apache.org/jira/browse/ARROW-7071
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 1.0.0
>
>
> NB: I'm not sure what kind of pitfalls there might be if replacing an existing validity bitmap and exposing some previously-null values
--
This message was sent by Atlassian Jira
(v8.3.4#803005)