[
https://issues.apache.org/jira/browse/HIVE-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563588#comment-14563588
]
Sergey Shelukhin commented on HIVE-4239:
----------------------------------------
Actually upon further examination SessionState is not meant to be thread-safe
in this way.
I am not sure why we don't have more bugs.
E.g. mapRedStats is a non-thread-safe map accessed during execution to put
values. It's not protected by compile lock or any other lock, so if 2 queries
execute within the same session it could have issues. Two "set" commands
running in parallel within the same session should have the same problem on
"hiveVariables" (see SetProcessor::setVariable calling get for that map and
modifying it
> Remove lock on compilation stage
> --------------------------------
>
> Key: HIVE-4239
> URL: https://issues.apache.org/jira/browse/HIVE-4239
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Query Processor
> Reporter: Carl Steinbach
> Assignee: Sergey Shelukhin
> Attachments: HIVE-4239.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
