You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "David Li (Jira)" <ji...@apache.org> on 2021/12/15 16:27:00 UTC
[jira] [Commented] (ARROW-15118) [C++] Cast kernel always creates and populates null bitmap
[ https://issues.apache.org/jira/browse/ARROW-15118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460072#comment-17460072 ]
David Li commented on ARROW-15118:
----------------------------------
Or as Antoine noted, we can generalize it and change INTERSECTION to not emit a null bitmap if all inputs have no nulls.
> [C++] Cast kernel always creates and populates null bitmap
> ----------------------------------------------------------
>
> Key: ARROW-15118
> URL: https://issues.apache.org/jira/browse/ARROW-15118
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Eduardo Ponce
> Priority: Minor
> Labels: kernel
> Fix For: 8.0.0
>
>
> Cast kernels seem to always create and populate the null bitmap even if the input data structure had a `nullptr` null bitmap. This automatic and extra allocation is not desirable, and not consistent.
> It seems some cast kernels use COMPUTED_NO_ALLOCATE and others use the default (INTERSECTION). We could change INTERSECTION to be a special-case of one input Array with no null bitmap. The expected behavior is that if the input has no nulls, don't bother emitting a null bitmap.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)