[
https://issues.apache.org/jira/browse/HBASE-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222919#comment-16222919
]
stack commented on HBASE-18770:
-------------------------------
I went back to have another look. The current operation execution engine works
with methods. The method signature can be anything. Method can optionally
return results. This precludes my being able to use return signaling bypass.
Given no other channel and not wanting to do hackery like
last-param-if-it-is-type-X-is-the-control object, I opted to hold to the
existing meta-channel facility, bypass in ObserverContext.
That said, on this reexamination, I see that I can simplify more and give
strong signal where bypass is not supported. Thanks.
Todo in here is fix unit tests, write unit tests to prove we have bypass for
all the CPs that were mentioned in the dev discussion, ensure that on bypass,
metrics are updated regardless (so we can get away with not exposing metrics to
Coprocessors), and finally, open up a few more methods. I'll be back soon.
> 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)
