You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Roee Shlomo (Jira)" <ji...@apache.org> on 2021/10/11 06:33:00 UTC

[jira] [Created] (ARROW-14271) [Java] Inconsistent logic for type IDs in Union vectors

Roee Shlomo created ARROW-14271:
-----------------------------------

             Summary: [Java] Inconsistent logic for type IDs in Union vectors
                 Key: ARROW-14271
                 URL: https://issues.apache.org/jira/browse/ARROW-14271
             Project: Apache Arrow
          Issue Type: Bug
          Components: Java
    Affects Versions: 6.0.0
            Reporter: Roee Shlomo


The current logic for calculating the type IDs in UnionVector#getField and DenseUnionVector#getField is:
 # DenseUnionVector uses an increasing counter 
 # UnionVector uses the ordinal of the type enum
 # Both completely ignore the type IDs provided at construction as part of fieldType (if provided)

We encountered this inconsistency while testing a direct roundtrip of a union vector between pyarrow and Java with the C Data Interface ('direct' here means without using VectorSchemaRoot/RecordBatch). The identifiers for the type IDs differ after completing a roundtrip. 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)