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

Jesse Yates commented on HBASE-7321:
------------------------------------

This strikes me as 'not really a snapshot' in that its very hard to reason 
about what writes will or won't be included in the snapshot, from a client 
perspective. To me (and maybe this is a group of 1) snapshot means 'at a point 
in time', but this is a far more ragged form. Traditionally, I believe 
snapshots are (the current state of the DB) - (uncommitted transactions), which 
for our case would be mutations that haven't completed when the snapshot starts.

Because we don't coordinate between regionservers, we can't give 'a point in 
time' as a reference, but rather a just a 'fuzzy' approximation (as you mention 
in the review, its an optimization on copytable), and therefore I don't feel 
that 'snapshot' is the best name for this operation as people could easily be 
confused by this. I'd be ok if you went with 'Fuzzy Snapshot' and a decent 
description (brings up case where we need to add a section to the refguide 
about the different types of snapshots with good descriptions)
                
> 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, pre-hbase-7321.v2.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

Reply via email to