[
https://issues.apache.org/jira/browse/HIVE-13193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15223551#comment-15223551
]
Carl Steinbach commented on HIVE-13193:
---------------------------------------
Changing the component from "HiveServer2" to "Query Processor" since
SessionState is not part of HS2.
[~aihuaxu], there have been some extensive discussions about the problems with
SessionState in other JIRAs and on the HiveDev mailing list. Someone also gave
a presentation about it at the last HiveContrib meetup. I think there is
general consensus that many of these problems stem from a bad mixture of thread
local and singleton design patterns in the SessionState class. Transitioning to
a simpler model where a per-Session object is explicitly passed into the
compiler and execution code paths would probably solve many of these issues.
This will require extensive changes to existing code, but don't let this
dissuade you -- our current problems with SessionState are largely the result
of many years of quick-fix solutions layered one atop another.
> Enable the complication in parallel in single session
> -----------------------------------------------------
>
> Key: HIVE-13193
> URL: https://issues.apache.org/jira/browse/HIVE-13193
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Aihua Xu
> Assignee: Aihua Xu
>
> Follow up on HIVE-4239. Investigate the needed change to support parallel
> complication in the same session.
> Some operation related stuff should be in OperationState rather than in
> SessionState.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
