[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Resolution: Fixed
Fix Version/s: 2.2.0
Status: Resolved (was: Patch Available)
Committed to master. Thanks [~Ferd] for the review!
> 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
> Fix For: 2.2.0
>
> Attachments: HIVE-15130.1.patch, HIVE-15130.2.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)
[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Attachment: HIVE-15130.2.patch
> 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-15130.2.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)
[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Attachment: (was: HIVE-15130.2.patch)
> 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-15130.2.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)
[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Attachment: HIVE-15130.2.patch
> 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-15130.2.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)
[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Attachment: HIVE-15130.1.patch
> 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)
[jira] [Updated] (HIVE-15130) Fixing shifting index issue related to object inspector caching
[
https://issues.apache.org/jira/browse/HIVE-15130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chao Sun updated HIVE-15130:
Status: Patch Available (was: Open)
> 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)
