[
https://issues.apache.org/jira/browse/HBASE-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102016#comment-13102016
]
Hudson commented on HBASE-4331:
-------------------------------
Integrated in HBase-TRUNK #2196 (See
[https://builds.apache.org/job/HBase-TRUNK/2196/])
HBASE-4331 Bypassing default actions in prePut fails sometimes with HTable
client
garyh :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/trunk/src/test/java/org/apache/hadoop/hbase/coprocessor/TestRegionObserverBypass.java
> Bypassing default actions in prePut fails sometimes with HTable client
> ----------------------------------------------------------------------
>
> Key: HBASE-4331
> URL: https://issues.apache.org/jira/browse/HBASE-4331
> Project: HBase
> Issue Type: Bug
> Components: coprocessors
> Affects Versions: 0.92.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.92.0
>
> Attachments: 4331-v2.txt, 4331-v3.txt, 4331-v4.txt, 4331.txt
>
>
> While testing some other scenario I found calling
> CoprocessorEnvironment.bypass() fails if all trailing puts in a batch are
> bypassed that way. By extension a single bypassed put will also fail.
> The problem is that the puts are removed from the batch in a way that does
> not align them with the result-status, and in addition the result is never
> marked as success.
> A possible fix is to just mark bypassed puts as SUCCESS and filter them in
> the following logic.
> (I also contemplated a new BYPASSED OperationStatusCode, but that turned out
> to be not necessary).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
