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

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/12610920/hbase-9221-trunk-v5.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 17 new 
or modified tests.

    {color:green}+1 hadoop1.0{color}.  The patch compiles against the hadoop 
1.0 profile.

    {color:green}+1 hadoop2.0{color}.  The patch compiles against the hadoop 
2.0 profile.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 1 
warning messages.

    {color:red}-1 javac{color}.  The applied patch generated 12 javac compiler 
warnings (more than the trunk's current 4 warnings).

    {color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

    {color:red}-1 site{color}.  The patch appears to cause mvn site goal to 
fail.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//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-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-v0.patch, 
> hbase-9221-0.96-v1.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, 
> hbase-9221-trunk-v5.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)

Reply via email to