[ https://issues.apache.org/jira/browse/HBASE-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ChiaPing Tsai updated HBASE-16933: ---------------------------------- Description: 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 was: 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 postBatchMutateIndispensably > 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 (v6.3.4#6332)