[jira] [Comment Edited] (HBASE-7801) Allow a deferred sync option per Mutation.

["Anoop Sam John (JIRA)" <ji...@apache.org>]

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

Anoop Sam John edited comment on HBASE-7801 at 3/12/13 12:25 PM:
-----------------------------------------------------------------

Change of writeToWAL -> writeGuarantee not handled in all the places? 
eg: Delete.java - Delete(final Delete d)
Put(Put putToCopy)
etc
                
      was (Author: anoopsamjohn):
    Change of writeToWAL -> writeTwriteGuarantee not handled in all the places? 
eg: Delete.java - Delete(final Delete d)
                  
> Allow a deferred sync option per Mutation.
> ------------------------------------------
>
>                 Key: HBASE-7801
>                 URL: https://issues.apache.org/jira/browse/HBASE-7801
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 0.95.0, 0.94.6
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.95.0, 0.98.0, 0.94.7
>
>         Attachments: 7801-0.94-v1.txt, 7801-0.94-v2.txt, 7801-0.94-v3.txt, 7801-0.96-full-v2.txt, 7801-0.96-v1.txt
>
>
> Won't have time for parent. But a deferred sync option on a per operation basis comes up quite frequently.
> In 0.96 this can be handled cleanly via protobufs and 0.94 we can have a special mutation attribute.
> For batch operation we'd take the safest sync option of any of the mutations. I.e. if there is at least one that wants to be flushed we'd sync the batch, if there's none of those but at least one that wants deferred flush we defer flush the batch, etc.

--
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