hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3876) call resetValid instead of ensureCapacity in the constructor of BytesRefArrayWritable
Date Sun, 13 Jan 2013 00:06:12 GMT

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

Ashutosh Chauhan commented on HIVE-3876:
----------------------------------------

Looks like it was a bug. +1 Running tests now.
                
> call resetValid instead of ensureCapacity in the constructor of BytesRefArrayWritable
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-3876
>                 URL: https://issues.apache.org/jira/browse/HIVE-3876
>             Project: Hive
>          Issue Type: Improvement
>          Components: Serializers/Deserializers
>    Affects Versions: 0.10.0
>            Reporter: Yin Huai
>            Assignee: Yin Huai
>            Priority: Minor
>         Attachments: HIVE-3876.1.patch.txt
>
>
> In the constructor of BytesRefArrayWritable, ensureCapacity(capacity) is called, but
"valid" has not been adjusted accordingly. After a new BytesRefArrayWritable has been created
with a initial capacity of "x", if resetValid() has not been called explicitly, the size returned
is still 0.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message