[
https://issues.apache.org/jira/browse/HIVE-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105065#comment-14105065
]
Hive QA commented on HIVE-7682:
-------------------------------
{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/12663183/HIVE-7682.1.patch
{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 6098 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_parquet_join
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver_dynpart_sort_opt_vectorization
org.apache.hive.jdbc.miniHS2.TestHiveServer2.testConnection
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/424/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/424/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-424/
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: 3 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12663183
> HadoopThriftAuthBridge20S should not reset configuration unless required
> ------------------------------------------------------------------------
>
> Key: HIVE-7682
> URL: https://issues.apache.org/jira/browse/HIVE-7682
> Project: Hive
> Issue Type: Bug
> Reporter: Brock Noland
> Assignee: Brock Noland
> Attachments: HIVE-7682.1.patch
>
>
> In HadoopThriftAuthBridge20S methods createClientWithConf and
> getCurrentUGIWithConf we create new Configuration objects so we can set the
> authentication type. When loading the new Configuration object, it looks like
> core-site.xml for the cluster it's connected to.
> This causes issues for Oozie since oozie does not have access to the
> core-site.xml as it's cluster agnostic.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
