[
https://issues.apache.org/jira/browse/HBASE-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222535#comment-16222535
]
stack commented on HBASE-18770:
-------------------------------
[~Apache9]
bq. So we will still have a bypass method for ObserverContext but for most
methods which can not be bypassed it will just like a noop? Pity...
Yes. This is how it works now. The bypass and complete methods remain in place
in ObserverContext but they only 'work' if invoking method allows bypass.
Javadoc on the method says whether bypass is allowed. Minimal change.
The execution engine needs a meta-channel to indicate 'bypass' and whether to
terminate execution. I got pretty far with a boolean return but I was writing a
new execution path and foresaw it taking a good amount of time to get right.
Let me have another look. I have better understanding of how this all works
now. Will report back.
> Remove bypass method in ObserverContext and implement the 'bypass' logic case
> by case
> -------------------------------------------------------------------------------------
>
> Key: HBASE-18770
> URL: https://issues.apache.org/jira/browse/HBASE-18770
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Assignee: stack
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18770.master.001.patch,
> HBASE-18770.master.002.patch
>
>
> http://search-hadoop.com/m/HBase/YGbbXd0RDCIHSC1
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
