[
https://issues.apache.org/jira/browse/HIVE-6679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247416#comment-14247416
]
Hive QA commented on HIVE-6679:
-------------------------------
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12687301/HIVE-6679.4.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 6703 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udaf_covar_pop
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2081/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/2081/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-2081/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12687301 - PreCommit-HIVE-TRUNK-Build
> 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)
