You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tephra.apache.org by "Andreas Neumann (JIRA)" <ji...@apache.org> on 2017/09/14 01:32:00 UTC

[jira] [Resolved] (TEPHRA-219) Setup proper security context in co-processor for compaction and flushes

     [ https://issues.apache.org/jira/browse/TEPHRA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Neumann resolved TEPHRA-219.
------------------------------------
    Resolution: Fixed

Remaining refactoring work will be done in TEPHRA-262

> Setup proper security context in co-processor for compaction and flushes
> ------------------------------------------------------------------------
>
>                 Key: TEPHRA-219
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-219
>             Project: Tephra
>          Issue Type: Sub-task
>            Reporter: Poorna Chandra
>            Assignee: Poorna Chandra
>             Fix For: 0.13.0-incubating
>
>
> From PHOENIX-3037, HBASE-16115 and HBASE-16141 - HBase runs compaction/flush co-processor hooks as the user (current user) who started the compaction/flush. This becomes an issue when a co-processor makes cross region server calls in hooks. If the calls are made as the current user, then the call may fail since the current user may not have sufficient privileges to perform the call.
> Tephra TransactionProcessor will need to run all calls in compaction/flush hooks as the login user instead of the current user.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)