hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ChiaPing Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16933) Calls to ObserverContext#bypass in HRegion#processRowsWithLocks are inconsistent
Date Mon, 21 Nov 2016 08:36:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682897#comment-15682897

ChiaPing Tsai commented on HBASE-16933:

The processRowsWithLocks() should have same use of cp hook as batchMutate(). Otherwise, the
observer development will go difficult because observer doesn’t know which method calls
the cp hook. The next patch will address it.
Any comment?

> Calls to ObserverContext#bypass in HRegion#processRowsWithLocks are inconsistent
> --------------------------------------------------------------------------------
>                 Key: HBASE-16933
>                 URL: https://issues.apache.org/jira/browse/HBASE-16933
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ChiaPing Tsai
>            Priority: Minor
>         Attachments: HBASE-16933.v0.patch
> The scenario is similar to [HBASE-15417|https://issues.apache.org/jira/browse/HBASE-15417].
> The MultiRowMutationProcessor has the incorrect usage of bypassed mutations.
> This patch makes some incompatible change shown below.
> # If any mutation is bypassed, all mutations will be bypassed. Because the RowMutations
is an atomic operation.
> # No CP post-hook will be called if the all mutations are bypassed. For example, postPut,
postDelete, and postBatchMutate

This message was sent by Atlassian JIRA

View raw message