arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Le Dem (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARROW-273) Lists use unsigned offset vectors instead of signed (as defined in the spec)
Date Thu, 25 Aug 2016 23:36:20 GMT

    [ https://issues.apache.org/jira/browse/ARROW-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15438131#comment-15438131
] 

Julien Le Dem commented on ARROW-273:
-------------------------------------

[~jnadeau], [~wesmckinn]: actually I'd be tempted to change the spec to make it an unsigned
int32 vector.
We said that it would be signed to make it easier for java. However we already support unsigned
types and the java implementation already uses an unsigned vector for this.
Thoughts?

[~jnadeau], [~sphillips]: I see that the Accessor and Mutator for UInt4Vector use the java
type int for values. How is the evaluation of an expression on such an unsigned value in a
signed type interpreted?

> Lists use unsigned offset vectors instead of signed (as defined in the spec)
> ----------------------------------------------------------------------------
>
>                 Key: ARROW-273
>                 URL: https://issues.apache.org/jira/browse/ARROW-273
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java - Vectors
>            Reporter: Julien Le Dem
>
> The List vector defines it's offset vector as UInt4Vector. (unsigned int 34)
> According to the arrow spec it should be a signed int32.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message