Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 11 Jan 2013 15:04:12 +0000 (UTC)
From: "Yin Huai (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12626852.1357766784955.120418.1357916652681@arcas>
In-Reply-To: <JIRA.12626852.1357766784955@arcas>
References: <JIRA.12626852.1357766784955@arcas>
Subject: [jira] [Updated] (HIVE-3876) call resetValid instead of
 ensureCapacity in the constructor of BytesRefArrayWritable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yin Huai updated HIVE-3876:
---------------------------

    Status: Patch Available  (was: Open)
    
> 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