hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Tomar (JIRA)" <>
Subject [jira] [Commented] (HIVE-3168) LazyBinaryObjectInspector.getPrimitiveJavaObject copies beyond length of underlying BytesWritable
Date Fri, 06 Jul 2012 11:10:34 GMT


Neha Tomar commented on HIVE-3168:

Tried the given suggestion. Replaced everything, but still same issue. Not sure where I am
making the mistake. I am using hcatalog released version 0.4.0. Can you please confirm if
there is no change in this hcatalog code.
> LazyBinaryObjectInspector.getPrimitiveJavaObject copies beyond length of underlying BytesWritable
> -------------------------------------------------------------------------------------------------
>                 Key: HIVE-3168
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>    Affects Versions: 0.9.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.10.0, 0.9.1
>         Attachments: HIVE-3168.1.patch, HIVE-3168.2.patch
> LazyBinaryObjectInspector.getPrimitiveJavaObject copies the full capacity of the LazyBinary's
underlying BytesWritable object, which can be greater than the size of the actual contents.

> This leads to additional characters at the end of the ByteArrayRef returned. When the
LazyBinary object gets re-used, there can be remnants of the later portion of previous entry.

> This was not seen while reading through hive queries, which I think is because a copy
elsewhere seems to create LazyBinary with length == capacity. (probably LazyBinary copy constructor).
This was seen when MR or pig used Hcatalog to read the data.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message