[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645109#comment-15645109
]
ASF GitHub Bot commented on HIVE-15130:
---------------------------------------
GitHub user sunchao opened a pull request:
https://github.com/apache/hive/pull/112
HIVE-15130: Fixing shifting index issue related to object inspector c…
…aching
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sunchao/hive fixing-cache-index
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/112.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #112
----
commit 605299e1a75761b5499a10cee7df752fc56f35e7
Author: Chao Sun <[email protected]>
Date: 2016-11-04T16:26:36Z
HIVE-15130: Fixing shifting index issue related to object inspector caching
----
> Fixing shifting index issue related to object inspector caching
> ---------------------------------------------------------------
>
> Key: HIVE-15130
> URL: https://issues.apache.org/jira/browse/HIVE-15130
> Project: Hive
> Issue Type: Sub-task
> Components: Reader
> Reporter: Chao Sun
> Assignee: Chao Sun
> Attachments: HIVE-15130.1.patch
>
>
> Hive caches object inspector in memory to avoid recreating the same object.
> However, in {{ArrayWritableObjectInspector}}, the {{equals}} and {{hashCode}}
> doesn't take account on all attributes of the class, therefore, even though
> the internal state (e.g., {{adjustedIndex}}) is different, it could still be
> mapped to the same result. This could cause wrong field index being used when
> reading Parquet data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
