[
https://issues.apache.org/jira/browse/HBASE-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218083#comment-16218083
]
stack commented on HBASE-18770:
-------------------------------
.001 is start. See edit of RegionObserver to see how it does bypass semantic
per method-call. Unfortunately, I can't paint all methods w/ the one color; how
bypass is done per method. Would appreciate a review. Next up is my making sure
these bypasses all work, have test coverage, etc.
A CP can't bypass flush. I'm thinking that CP won't have enough info to block a
flush and even then, it would have to schedule and then wait on completion
before progressing.
A CP can 'cancel' a compaction by returning empty set of files to compact. This
is how has always been.
> 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
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18770.master.001.patch
>
>
> http://search-hadoop.com/m/HBase/YGbbXd0RDCIHSC1
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
