hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
Date Fri, 13 Sep 2013 01:24:54 GMT

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

Hadoop QA commented on HBASE-9221:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12602934/hbase-9221-trunk-v2.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 14 new or modified
tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/7203//console

This message is automatically generated.
                
> Provide interface for getting a User in the client
> --------------------------------------------------
>
>                 Key: HBASE-9221
>                 URL: https://issues.apache.org/jira/browse/HBASE-9221
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, hadoop2, security
>    Affects Versions: 0.98.0, 0.95.2, 0.94.12
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.98.0, 0.94.13, 0.96.1
>
>         Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-trunk-v0.patch,
hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch
>
>
> Sometimes, users will want to provide their own User class depending on the type of security
they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs
CDH means potentially different ways of getting the UserGroupInformation. 
> This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User
to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as
supporting custom authentication code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message