[
https://issues.apache.org/jira/browse/HIVE-14239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382349#comment-15382349
]
Aihua Xu commented on HIVE-14239:
---------------------------------
Seems it causes backward-incompatibility for the clients. Maybe it's not worth
it. I will investigate if it can be achieved without adding sessionHandle in
the thrift OperationHandle class.
> Change OperationManager to serve each session and make it threadsafe
> --------------------------------------------------------------------
>
> Key: HIVE-14239
> URL: https://issues.apache.org/jira/browse/HIVE-14239
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Affects Versions: 2.0.1
> Reporter: Aihua Xu
> Assignee: Aihua Xu
> Attachments: HIVE-14239.1.patch
>
>
> Currently OperationManager is designed to hold all the operations from all
> the sessions. It will cause the functions to unnecessarily sync between the
> operations across the sessions. And also there are some functions are not
> threadsafe which could be the cause for invalid OperationHandle.
> Plan to change OperationManager to just serve one session and make it a
> helper class for HiveSession rather than a service which doesn't seem to be
> needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
