hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-7801) Allow a deferred sync option per Mutation.
Date Thu, 21 Feb 2013 20:06:15 GMT

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

Enis Soztutar edited comment on HBASE-7801 at 2/21/13 8:05 PM:
---------------------------------------------------------------

bq. As far the Java API in concerned the fact that we use PB is an implementation detail and
should not leak out.
My argument above is definitely longer term, when we decide to officially support multi-language
clients. 

bq. Are you also suggesting changing the Mutation API? I.e. remove (set|get)WriteToWAL and
replace it with setWriteGuarantee(WriteGuarantee wg)
we can do both. Add the enums in the java client API, and the PB serialization. We can deprecate
(set|get)WriteToWAL() in 0.94, and remove in 0.96. 

                
      was (Author: enis):
    bq. As far the Java API in concerned the fact that we use PB is an implementation detail
and should not leak out.
My argument above is definitely longer term, when we decide to officially support multi-language
clients. 
bq. Are you also suggesting changing the Mutation API? I.e. remove {set|get}WriteToWAL and
replace it with setWriteGuarantee(WriteGuarantee wg)?
Yes, we can do both. Add the enums in the java client API, and the PB serialization. We can
deprecate {set|get}WriteToWAL() in 0.94, and remove in 0.96. 

                  
> 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

Mime
View raw message