[
https://issues.apache.org/jira/browse/HIVE-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811126#comment-13811126
]
Hive QA commented on HIVE-5715:
-------------------------------
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12611493/HIVE-5715.2.patch
{color:green}SUCCESS:{color} +1 4547 tests passed
Test results:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/101/testReport
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/101/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> HS2 should not "start" a session for every command
> --------------------------------------------------
>
> Key: HIVE-5715
> URL: https://issues.apache.org/jira/browse/HIVE-5715
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Attachments: HIVE-5715.1.patch, HIVE-5715.2.patch
>
>
> HS2 calls SessionState.start multiple times (acquire, operation.run) - where
> it really just cares that the session is set in the thread local store. There
> are some calls in start session method now that preload stuff that's used
> during the session. Instead of doing that over and over again, I think it'd
> be nicer for HS2 to start a session once and then just do the thread local
> magic as needed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
