[ https://issues.apache.org/jira/browse/HIVE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248013#comment-14248013 ]
Lefty Leverenz commented on HIVE-6679: -------------------------------------- Doc note: Patch 4 adds two configuration parameters (which are different from the two in patch 1): *hive.server2.tcp.socket.blocking.timeout* and *hive.server2.tcp.socket.keepalive*. Code review: The time specification for *hive.server2.tcp.socket.blocking.timeout* could be done with a TimeValidator like others in HiveConf.java since 0.14.0, for example: {code} METASTORE_CLIENT_CONNECT_RETRY_DELAY("hive.metastore.client.connect.retry.delay", "1s", new TimeValidator(TimeUnit.SECONDS), {code} > 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, HIVE-6679.4.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)