You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ChiaPing Tsai (JIRA)" <ji...@apache.org> on 2016/10/05 07:14:20 UTC

[jira] [Comment Edited] (HBASE-16768) Inconsistent results from the Append/Increment

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

ChiaPing Tsai edited comment on HBASE-16768 at 10/5/16 7:14 AM:
----------------------------------------------------------------

hi [~stack]

{noformat}
We have to iterate twice?
{noformat}
That is ugly code... i will fix it.

{noformat}
This is a branch-1 only issue?
{noformat}
master have this issue also.

Thanks for your review.



was (Author: chia7712):
hi [~stack]

{noformat}
We have to iterate twice?
{noformat}
That is ugly code... i will fix it.

{noformat}
This is a branch-1 only issue?
{noformat}
master have this issue also.

Thanks for you review.


> Inconsistent results from the Append/Increment
> ----------------------------------------------
>
>                 Key: HBASE-16768
>                 URL: https://issues.apache.org/jira/browse/HBASE-16768
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ChiaPing Tsai
>            Priority: Minor
>         Attachments: HBASE-16768.v0.patch
>
>
> If the Append/Increment skips the WAL, the sequential id will not be updated.
> It introduces that the AbstractMemStore#upsert may remove the cell even though the cell is visible to the oldest scanner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)