hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
Date Mon, 28 Oct 2013 23:42:31 GMT

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

Jesse Yates commented on HBASE-9221:
------------------------------------

default is the current behavior - we will always do as we have done, unless you make your
own class to do something else. That should just be a module move for the user class.

HBaseProto was not intended, fixed in next patch.

> 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.96.1, 0.94.14
>
>         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, hbase-9221-trunk-v3.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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message