You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[arrow-vector] Zero-copy transfer of DecimalVector and Decimal256Vector is losing nullability information #692
Describe the bug, including details regarding any error messages, version, and platform.
In the main branch, DecimalVector and Decimal256Vector are losing nullability information during a zero-copy transfer. It currently forces a nullable FieldType onto the "to" ValueVector.
The deficiency in the code is in DecimalVector.TransferImpl class when trying to get a transfer getTransferPair(String, BufferAllocator) creating a DecimalVector with a nullable FieldType (although the "from" ValueVector's FieldType is non-nullable):
Note that all the other (at least the primitive) ValueVectors are transferred without losing nullability information by using the "from" ValueVector's field. E.g.:
Activity
GH-692: Preserve nullability information while transfering DecimalVec…
apacheGH-692: Preserve nullability information while transfering Deci…
apacheGH-692: Preserve nullability information while transfering Deci…
apacheGH-692: Preserve nullability information while transfering Deci…