[
https://issues.apache.org/jira/browse/HIVE-14888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834482#comment-16834482
]
Hive QA commented on HIVE-14888:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12967968/HIVE-14888.5.patch
{color:red}ERROR:{color} -1 due to no test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 15982 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/17146/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/17146/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-17146/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12967968 - PreCommit-HIVE-Build
> SparkClientImpl checks for "kerberos" string in hiveconf only when
> determining whether to use keytab file.
> ----------------------------------------------------------------------------------------------------------
>
> Key: HIVE-14888
> URL: https://issues.apache.org/jira/browse/HIVE-14888
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Thomas Rega
> Assignee: David McGinnis
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-14888.1-spark.patch, HIVE-14888.2.patch,
> HIVE-14888.3.patch, HIVE-14888.4.patch, HIVE-14888.5.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> The SparkClientImpl will only provide a principal and keytab argument if the
> HADOOP_SECURITY_AUTHENTICATION in hive conf is set to "kerberos". This will
> not work on clusters with Hadoop security enabled that are not configured as
> "kerberos", for example, a cluster which is configured for "ldap".
> The solution is to call UserGroupInformation.isSecurityEnabled() instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
