[
https://issues.apache.org/jira/browse/HIVE-11512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791290#comment-14791290
]
Hive QA commented on HIVE-11512:
--------------------------------
{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/12756286/HIVE-11512.patch
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 9445 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation
org.apache.hive.hcatalog.streaming.TestStreaming.testInterleavedTransactionBatchCommits
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5304/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5304/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5304/
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: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12756286 - PreCommit-HIVE-TRUNK-Build
> Hive LDAP Authenticator should also support full DN in Authenticate()
> ----------------------------------------------------------------------
>
> Key: HIVE-11512
> URL: https://issues.apache.org/jira/browse/HIVE-11512
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 1.1.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Minor
> Attachments: HIVE-11512.patch
>
>
> In certain LDAP implementation, LDAP Binding can occur using the full DN for
> the user. Currently, LDAPAuthentication Provider assumes that the username
> passed into Authenticate() is a short username & not a full DN. While the
> initial bind works fine either way, the filter code is reliant on it being a
> shortname.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
