[jira] [Commented] (HIVE-6679) HiveServer2 should support configurable the server side socket timeout and keepalive for various transports types where applicable

["Lefty Leverenz (JIRA)" <ji...@apache.org>]

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

Lefty Leverenz commented on HIVE-6679:
--------------------------------------

Currently this shows status Patch Available and resolution Unresolved because there's a patch for 1.1.0, although the 1.0.0 patch was committed and it is included in the release.  (I checked HiveConf.java for *hive.server2.tcp.socket.blocking.timeout* and *hive.server2.tcp.socket.keepalive* but didn't check other patch changes.)

Unfortunately the 1.0.0 release notes linked to the downloads page don't include this issue.  There may be other JIRA issues that were fixed in 1.0.0 but fell off the back of the cart when 0.15 was changed to 1.1 and then to 1.1.0.

* [1.0.0 release notes | https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329278&styleName=Text&projectId=12310843]

> HiveServer2 should support configurable the server side socket timeout and keepalive for various transports types where applicable
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 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
>              Labels: TODOC1.0, TODOC15
>             Fix For: 1.1.0
>
>         Attachments: HIVE-6679.1.patch.txt, HIVE-6679.2.patch.txt, HIVE-6679.3.patch, HIVE-6679.4.patch, HIVE-6679.5.patch, HIVE-6679.6.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)