[
https://issues.apache.org/jira/browse/HBASE-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189981#comment-16189981
]
Andrew Purtell commented on HBASE-18127:
----------------------------------------
bq. 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.
The way I see it, although the patch only adds this for batchMutate code paths,
it should be generic enough so we can drop the same solution on other code
paths as needed without cloning code or changing the interface. See my RB
comments in this regard. [~anoop.hbase]
bq. In every mutation related flow, there are 4 hook points at least. preXXX,
preStartRegionOperation, postStartRegionOperation and postXXX.
I think this is a good point and [~abhishek.chouhan] should talk with [~appy]
about how this fits in with the changes going in for 2.0 . We would also like
this specific change on the branch-1's to help coprocessor applications like
Phoenix so the current proposed scope is only exactly where it is needed for
that.
> 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)
