hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13194) Hive object is not thread safe, is shared via a threadlocal and thus should not be shared via session - part 2
Date Thu, 14 Apr 2016 14:09:25 GMT

    [ https://issues.apache.org/jira/browse/HIVE-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241208#comment-15241208
] 

Aihua Xu commented on HIVE-13194:
---------------------------------

[~sershe] The HMSClient inside Hive object right now is thread-safe after HIVE-10956. So what
I think is, when the query starts to compile, we create a Hive object for it and then it will
not change during its life time. Seems we can remove the threadlocal for Hive object. Do you
see any drawback on that? I feel we can simplify the logic on this.

Can you elaborate what are we trying to do in this patch?

> Hive object is not thread safe, is shared via a threadlocal and thus should not be shared
via session - part 2
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13194
>                 URL: https://issues.apache.org/jira/browse/HIVE-13194
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-13194.patch
>
>
> Session has session Hive object stored in a field. Given that Hive object is not thread
safe and is also taken from a threadlocal to start with, that is not a good idea.



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

Mime
View raw message