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

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 7.0.0
• Component/s: Java
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/30257
• Assignee: Chao Sun
• Reporter: Chao Sun
• Created: 16/Nov/21 00:27
• Updated: 11/Jan/23 08:41
• Resolved: 14/Dec/21 18:37

Description

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.

Issue Links

• links to: GitHub Pull Request #11709