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-16217) Identify calling user in ObserverContext
Date Wed, 05 Apr 2017 23:23:41 GMT

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

Hadoop QA commented on HBASE-16217:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 15s {color} | {color:red}
HBASE-16217 does not apply to branch-1. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12820863/HBASE-16217.branch-1.001.patch
|
| JIRA Issue | HBASE-16217 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/6342/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> Identify calling user in ObserverContext
> ----------------------------------------
>
>                 Key: HBASE-16217
>                 URL: https://issues.apache.org/jira/browse/HBASE-16217
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors, security
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16217.branch-1.001.patch, HBASE-16217.master.001.patch, HBASE-16217.master.002.patch,
HBASE-16217.master.003.patch
>
>
> We already either explicitly pass down the relevant User instance initiating an action
through the call path, or it is available through RpcServer.getRequestUser().  We should carry
this through in the ObserverContext for coprocessor upcalls and make use of it for permissions
checking.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message