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

stack updated HBASE-19048:
--------------------------
      Resolution: Fixed
    Release Note: 
Purged InterfaceAudience.Private parameters from methods in MasterObserver.

preAbortProcedure no longer takes a ProcedureExecutor.

postGetProcedures no longer takes a list of Procedures.

postGetLocks no longer takes a list of locks.

preRequestLock and postRequestLock no longer take lock type.

preLockHeartbeat and postLockHeartbeat no longer takes a lock procedure.

The implication is that that the Coprocessors that depended on these params 
have had to coarsen so for example, the AccessController can not do access per 
Procedure or Lock but rather, makes a judgement on the general access (You'll 
need to be ADMIN to see list of procedures and locks).
          Status: Resolved  (was: Patch Available)

Pushed to master and branch-2 after purging unused imports. Thanks for the 
reviews lads.

> Cleanup MasterObserver hooks which takes IA private params
> ----------------------------------------------------------
>
>                 Key: HBASE-19048
>                 URL: https://issues.apache.org/jira/browse/HBASE-19048
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Anoop Sam John
>            Assignee: stack
>             Fix For: 2.0.0-alpha-4
>
>         Attachments: HBASE-19048.master.001.patch, 
> HBASE-19048.master.002.patch, HBASE-19048.master.003.patch, 
> HBASE-19048.master.003.patch
>
>
> These are the ones in MasterObserver
> {code}
>               preAbortProcedure        -  ProcedureExecutor
>               postGetProcedures        - Procedure
>               postGetLocks             - LockedResource
>               preRequestLock   - LockType
>               postRequestLock  - LockType
>               preLockHeartbeat         - LockProcedure
>               postLockHeartbeat        - LockProcedure
> {code}



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

Reply via email to