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

Lars Hofhansl edited comment on HBASE-7801 at 2/16/13 11:59 PM:
----------------------------------------------------------------

Here's a 0.96 patch. Also uses Mutation attributes to avoid PB changes (could 
do this through PB as well).
Again, Increment is not supported as it does not extend Mutation (but it could 
be supported if we make an PB change).

0.96 has RowProcessors, so I added an internal API to allow a row processor to 
decided whether it requests a sync. By default the response is true.
                
      was (Author: lhofhansl):
    Here's a 0.96 patch. Also uses Mutation attributes to avoid PB changes 
(could do this through PB as well).
Again, Increment is not supported as it does not extend Mutation (but it could 
be supported if we make an RPC change).

0.96 has a RowProcessors, so I added an internal API to allow the processor to 
decided whether it requests a sync. By default the response is true.
                  
> 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
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>             Fix For: 0.96.0, 0.94.6
>
>         Attachments: 7801-0.94-v1.txt, 7801-0.94-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

Reply via email to