You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2018/10/15 18:52:00 UTC

[jira] [Commented] (SENTRY-2427) Use Hadoop KerberosName class to derive shortName

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

Hadoop QA commented on SENTRY-2427:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12943985/SENTRY-2427.01.patch against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to build with patch (exit code 1)

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/4178/console

This message is automatically generated.

> Use Hadoop KerberosName class to derive shortName
> -------------------------------------------------
>
>                 Key: SENTRY-2427
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2427
>             Project: Sentry
>          Issue Type: New Feature
>          Components: Sentry
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>         Attachments: SENTRY-2427.01.patch
>
>
> Sentry doesn't use auth to local group mapping hadoop configuration. We may have a use case for cross realm users to have access to sentry service and in which case Sentry needs to have access to those configurations. Switching to using KerberosName will handle that case and other cases as well



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)