You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2011/09/08 01:24:09 UTC
[jira] [Commented] (HBASE-4331) Bypassing default actions in prePut
fails sometimes with HTable client
[ https://issues.apache.org/jira/browse/HBASE-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099654#comment-13099654 ]
Lars Hofhansl commented on HBASE-4331:
--------------------------------------
What's the general feeling about this change?
> 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.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