[
https://issues.apache.org/jira/browse/HBASE-18127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264980#comment-16264980
]
Abhishek Singh Chouhan commented on HBASE-18127:
------------------------------------------------
The cases that i saw had all the coproc hooks related to an operation being
executed by a single thread. Do we have cases where some coproc hooks are
executed by one thread and other by some other thread so we need to pass state
between them? (need to check more here). For the general case where a thread
from some pool executes the operation involving coproc hooks (all hooks related
to that operation), i was thinking maybe we could have a util class that
subclasses ThreadPoolExecutor and set the thread local in beforeExecute and
remove in afterExecute, and then we use this threadpool whereever we're using
threadpools for operations that involve coproc hooks.
> 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)