You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/11/16 01:17:00 UTC

[jira] [Updated] (ARROW-14718) [Java] loadValidityBuffer should avoid allocating memory when input is not null and there are only null or non-null values

     [ https://issues.apache.org/jira/browse/ARROW-14718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ARROW-14718:
-----------------------------------
    Labels: pull-request-available  (was: )

> [Java] loadValidityBuffer should avoid allocating memory when input is not null and there are only null or non-null values
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-14718
>                 URL: https://issues.apache.org/jira/browse/ARROW-14718
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Java
>            Reporter: Chao Sun
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently in {{BitVectorHelper.loadValidityBuffer}}, we always allocate memory when the source vector contains only null or non-null values. However, as the format also allows allocating validity buffer even if all values are null or not-null, the method should also consider whether the input validity buffer is null or not, and avoiding allocating new buffer when it is latter.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)