[ARROW-5583] [Java] When the isSet of a NullableValueHolder is 0, the buffer field should not be used

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Component/s: Java
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/22025
• Assignee: Liya Fan
• Reporter: Liya Fan
• Created: 13/Jun/19 10:28
• Updated: 11/Jan/23 07:41
• Resolved: 19/Jun/19 05:21

Description

For each variable-width vector, like the VarCharVector, it has a set method that uses a NullableValueHolder as the input parameter. When the isSet field is set to 0, it means the value to set is null, so the buffer field of the NullableValueHolder is invalid, and should not be used.

For example, the user may set a null value in the VarCharVector with the following code snippet:

NullableVarCharHolder holder = new NullableVarCharHolder();
holder.isSet = 0;
...
varCharVector.set(i, holder);

Please note that in the code above, the holder.buffer is not set, so it is null. According to the VarCharVector#set method, it will set the bytes using holder.buffer even if holder.isSet equals 0. This will lead to an exception.

Issue Links

• links to: GitHub Pull Request #4543