[
https://issues.apache.org/jira/browse/HIVE-12949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122795#comment-15122795
]
Hive QA commented on HIVE-12949:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12784782/HIVE-12949.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 10021 tests
executed
*Failed tests:*
{noformat}
TestMiniTezCliDriver-script_pipe.q-tez_smb_empty.q-subquery_in.q-and-12-more -
did not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_authorization_uri_import
org.apache.hive.jdbc.TestJdbcWithMiniHS2.testAddJarDataNucleusUnCaching
org.apache.hive.jdbc.TestSSL.testSSLVersion
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6783/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6783/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-6783/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
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: 12784782 - PreCommit-HIVE-TRUNK-Build
> Fix description of hive.server2.logging.operation.level
> -------------------------------------------------------
>
> Key: HIVE-12949
> URL: https://issues.apache.org/jira/browse/HIVE-12949
> Project: Hive
> Issue Type: Bug
> Components: Configuration
> Reporter: Mohit Sabharwal
> Assignee: Mohit Sabharwal
> Attachments: HIVE-12949.patch
>
>
> Description of {{hive.server2.logging.operation.level}} states that this
> property is available to set at session level. This is not correct. The
> property is only settable at HS2 level currently.
> A log4j appender is created just once currently - based on logging level
> specified by this config, at OperationManager init time in
> initOperationLogCapture(). And there is only one instance of OperationManager.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
