[
https://issues.apache.org/jira/browse/HBASE-16217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819891#comment-16819891
]
Hudson commented on HBASE-16217:
--------------------------------
Results for branch branch-1
[build #777 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/777/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/777//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/777//JDK7_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/777//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> 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
> Priority: Major
> Fix For: 2.0.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
(v7.6.3#76005)
