hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HIVE-10219) BytesBytesMultiHashMap::clear() can't be concurrently used with reads
Date Tue, 07 Apr 2015 19:02:14 GMT

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

Sergey Shelukhin resolved HIVE-10219.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: llap

Fixed in branch by making clear a no-op for now (discardData method used for Hybrid case)

> BytesBytesMultiHashMap::clear() can't be concurrently used with reads
> ---------------------------------------------------------------------
>
>                 Key: HIVE-10219
>                 URL: https://issues.apache.org/jira/browse/HIVE-10219
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Gopal V
>            Assignee: Sergey Shelukhin
>             Fix For: llap
>
>
> The semantics of the HashMap::clear() is unclear for concurrent access.
> With HIVE-10128 fixes, the only remaining thread-safety concern is the behaviour of clear()
calls.
> Concurrent usage + clearing from HybridHash and VectorMapJoin operator will result in
race conditions.
> There is no valid clear() operations possible without knowledge of the cached nature
and the ref-count of each hashtable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message