[
https://issues.apache.org/jira/browse/HBASE-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221326#comment-16221326
]
stack commented on HBASE-18770:
-------------------------------
.002 Abandons all previous attempts at a grand change and instead settles for a
relatively minor change; default to NOT allow bypass and then add flag to
executors which is true when a method is bypassable. I kept the 'bypass' in
ObserverContext (I needed meta state kept somewhere...) and I kept the
'complete' too. Semantic is that 'complete' only applies if 'bypass' is set.
This is a gross simplification.
Let me see what I've broken with this change.
TODO: Figure the scanner methods that don't say they do but actually do
'bypass' and add tests to prove new route.
TODO: Survey mailing list to make sure what I have here will work for all
examples cited.
(Sorry [[email protected]] -- I didn't have the courage to do the grand
sweeping change.. I'm a wuss).
> 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)
