hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-7801) Allow a deferred sync option per Mutation.
Date Thu, 14 Feb 2013 01:05:11 GMT

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

Lars Hofhansl edited comment on HBASE-7801 at 2/14/13 1:04 AM:
---------------------------------------------------------------

I tested the patch locally. Works fine.
Any comments?

I could do the same for 0.96, or make a proper protobuf change there. (btw. for setting the
cluster id in trunk we're still using attributes as opposed to encoding this in the protobuf
message).
It is actually an interesting question whether we should maintain optional Mutation attributes
via attributes or via a protobuf change.

                
      was (Author: lhofhansl):
    I testing the patch locally. Works fine.
Any comments?

I could do the same for 0.96, or make a proper protobuf change there. (btw. for setting the
cluster id in trunk we're still using attributes as opposed to encoding this in the protobuf
message).
It is actually an interesting question whether we should maintain optional Mutation attributes
via attributes or via a protobuf change.

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

Mime
View raw message