[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807535#comment-13807535
]
Jesse Yates commented on HBASE-9221:
------------------------------------
As far as I know, that's the only usage of it. Its package private for testing
(and is commented as such), so it seemed ok. Managed in the tests now (for
instance, TestSecureLoadIncrementalHFiles) by just setting the right config
values.
Offline mentioned the same to Lars and he is happy with the patch :)
Planning to commit this evening, unless there are objections.
> 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-0.94-v3.patch, hbase-9221-0.96-v0.patch,
> hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
> hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch,
> hbase-9221-trunk-v4.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)
