hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7553) avoid the scheduling maintenance window for every jar change
Date Tue, 02 Sep 2014 06:30:21 GMT

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

Hive QA commented on HIVE-7553:
-------------------------------



{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/12665837/HIVE-7553.3.patch

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 6139 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.session.TestSessionState.testReloadAuxJars[0]
org.apache.hadoop.hive.ql.session.TestSessionState.testReloadAuxJars[1]
org.apache.hadoop.hive.ql.session.TestSessionState.testReloadExistingAuxJars[0]
org.apache.hadoop.hive.ql.session.TestSessionState.testReloadExistingAuxJars[1]
{noformat}

Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/596/testReport
Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/596/console
Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-596/

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: 4 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12665837

> avoid the scheduling maintenance window for every jar change
> ------------------------------------------------------------
>
>                 Key: HIVE-7553
>                 URL: https://issues.apache.org/jira/browse/HIVE-7553
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>            Reporter: Ferdinand Xu
>            Assignee: Ferdinand Xu
>         Attachments: HIVE-7553.1.patch, HIVE-7553.2.patch, HIVE-7553.3.patch, HIVE-7553.patch,
HIVE-7553.pdf
>
>
> When user needs to refresh existing or add a new jar to HS2, it needs to restart it.
As HS2 is service exposed to clients, this requires scheduling maintenance window for every
jar change. It would be great if we could avoid that.



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

Mime
View raw message