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

Anoop Sam John commented on HBASE-18127:
----------------------------------------

So this is specific to the batchMutate flow which deals with pre/post 
put/Delete and the batch hooks?  Thought this u are adding as a generic one.  
For the Phoenix issue of knowing whether the handling was done in pre hook or 
not in preBatch hook, there was similar case in AC also once. See 
AccessController#CHECK_COVERING_PERM and its usage.  That might look as a 
workaround though. This seems more generic but am not sure whether we can call 
it generic as per this patch.  What if btw pre and post hooks one want to pass 
state ? (Like pre and post Append)
In every mutation related flow, there are 4 hook points at least.  preXXX, 
preStartRegionOperation, postStartRegionOperation and postXXX.


> Enable state to be passed between the region observer coprocessor hook calls
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-18127
>                 URL: https://issues.apache.org/jira/browse/HBASE-18127
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Lars Hofhansl
>            Assignee: Abhishek Singh Chouhan
>         Attachments: HBASE-18127.master.001.patch, 
> HBASE-18127.master.002.patch, HBASE-18127.master.002.patch, 
> HBASE-18127.master.003.patch, HBASE-18127.master.004.patch, 
> HBASE-18127.master.005.patch, HBASE-18127.master.005.patch, 
> HBASE-18127.master.006.patch
>
>
> Allow regionobserver to optionally skip postPut/postDelete when 
> postBatchMutate was called.
> Right now a RegionObserver can only statically implement one or the other. In 
> scenarios where we need to work sometimes on the single postPut and 
> postDelete hooks and sometimes on the batchMutate hooks, there is currently 
> no place to convey this information to the single hooks. I.e. the work has 
> been done in the batch, skip the single hooks.
> There are various solutions:
> 1. Allow some state to be passed _per operation_.
> 2. Remove the single hooks and always only call batch hooks (with a default 
> wrapper for the single hooks).
> 3. more?
> [~apurtell], what we had discussed a few days back.



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

Reply via email to