[jira] [Commented] (HIVE-6679) HiveServer2 should support configurable the server side socket timeout for all transports types

["Thejas M Nair (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247185#comment-14247185 ] 

Thejas M Nair commented on HIVE-6679:
-------------------------------------

The 3.patch does not have the http transport changes that were there in 2.patch. Is that intentional ?
I think enabling this by default makes sense, instead of having users set this if they run into issues. A timeout of around couple of minutes might be reasonable default.




> HiveServer2 should support configurable the server side socket timeout for all transports types
> -----------------------------------------------------------------------------------------------
>
>                 Key: HIVE-6679
>                 URL: https://issues.apache.org/jira/browse/HIVE-6679
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 0.13.0, 0.14.0
>            Reporter: Prasad Mujumdar
>            Assignee: Navis
>             Fix For: 0.14.1
>
>         Attachments: HIVE-6679.1.patch.txt, HIVE-6679.2.patch.txt, HIVE-6679.3.patch
>
>
>  HiveServer2 should support configurable the server side socket read timeout and TCP keep-alive option. Metastore server already support this (and the so is the old hive server). 
> We now have multiple client connectivity options like Kerberos, Delegation Token (Digest-MD5), Plain SASL, Plain SASL with SSL and raw sockets. The configuration should be applicable to all types (if possible).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)