You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Panagiotis Garefalakis (Jira)" <ji...@apache.org> on 2021/05/22 10:30:00 UTC

[jira] [Resolved] (HIVE-25142) Rehashing in map join fast hash table causing corruption for large keys

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

Panagiotis Garefalakis resolved HIVE-25142.
-------------------------------------------
    Resolution: Fixed

> Rehashing in map join fast hash table  causing corruption for large keys
> ------------------------------------------------------------------------
>
>                 Key: HIVE-25142
>                 URL: https://issues.apache.org/jira/browse/HIVE-25142
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> In map join the hash table is created using the keys. To support rehashing, the keys are stored in write buffer. The hash table contains the offset of the keys along with the hash code. When rehashing is done, the offset is extracted from the hash table and then hash code is generated again. For large keys of size greater than 255, the key length is also stored along with the key. In case of fast hash table implementation the way key is extracted is not proper. There is a code bug and thats causing the wrong key to be extracted and causing wrong hash code generation. This is causing the corruption in the hash table.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)