You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2012/12/31 21:42:12 UTC

[jira] [Comment Edited] (HBASE-7321) Simple Flush Snapshot

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

Jonathan Hsieh edited comment on HBASE-7321 at 12/31/12 8:40 PM:
-----------------------------------------------------------------

The unstability I mentioned was fixed in v4 of HBASE-6864
                
      was (Author: jmhsieh):
    The unstability I mentioned was fixed in v4 of HBSAE-6864
                  
> Simple Flush Snapshot
> ---------------------
>
>                 Key: HBASE-7321
>                 URL: https://issues.apache.org/jira/browse/HBASE-7321
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>         Attachments: hbase-7321.v2.patch, hbase-7321.v3.patch, hbase-7321.v4.patch, pre-hbase-7321.v2.patch, pre-hbase-7321.v3.patch, pre-hbase-7321.v4.patch
>
>
> This snapshot style just issues a region flush and then "snapshots" the region.  
> This is a simple implementation that gives the equivalent of copytable consistency.  While by most definitions of consistency if a client writes A and then write B to different region servers, only neither, only A, or both A+B writes should be present, this one allows the only B case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira