[ https://issues.apache.org/jira/browse/HBASE-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106681#comment-16106681 ]
Andrew Purtell commented on HBASE-18127: ---------------------------------------- I think making OperationContext a class and avoiding unnecessary Simple* or Default* implementation is better, because that is what we do with ObserverContext already. Just my opinion. > Allow regionobserver to optionally skip postPut/postDelete when > postBatchMutate was called > ------------------------------------------------------------------------------------------ > > 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 > > > 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)