[
https://issues.apache.org/jira/browse/HIVE-5799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828324#comment-13828324
]
Navis commented on HIVE-5799:
-----------------------------
It's the way I've solved this issue for oozie-hive integration. In that case,
we know that the all the connection is from single entity(oozie) and one more
connection was not big burden. But if connections are to be connected from
various entities, the number of connection for hive server2 would be simply
doubled. Would it be ok? Then I'll proceed the work.
> session/operation timeout for hiveserver2
> -----------------------------------------
>
> Key: HIVE-5799
> URL: https://issues.apache.org/jira/browse/HIVE-5799
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-5799.1.patch.txt, HIVE-5799.2.patch.txt,
> HIVE-5799.3.patch.txt
>
>
> Need some timeout facility for preventing resource leakages from instable or
> bad clients.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
