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

Hadoop QA commented on HBASE-8662:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12591325/trunk-8662_v7.1.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 3 new 
or modified tests.

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

    {color:red}-1 hadoop2.0{color}.  The patch failed to compile against the 
hadoop 2.0 profile.

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

This message is automatically generated.
                
> [rest] support impersonation
> ----------------------------
>
>                 Key: HBASE-8662
>                 URL: https://issues.apache.org/jira/browse/HBASE-8662
>             Project: HBase
>          Issue Type: Sub-task
>          Components: REST, security
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 0.98.0
>
>         Attachments: method_doas.patch, secure_rest.patch, trunk-8662.patch, 
> trunk-8662_v2.patch, trunk-8662_v3.patch, trunk-8662_v4.patch, 
> trunk-8662_v5.patch, trunk-8662_v6.patch, trunk-8662_v7.1.patch, 
> trunk-8662_v7.patch
>
>
> Currently, our client API uses a fixed user: the current user. It should 
> accept a user passed in, if authenticated.

--
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

Reply via email to