[
https://issues.apache.org/jira/browse/HBASE-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578472#comment-13578472
]
Lars Hofhansl commented on HBASE-7801:
--------------------------------------
The use case that I see a lot at Saleforce is similar to the writeToWAL use
case. By default the Mutation is written to the WAL unless the Mutation says
not to. The defer case is the same IMHO.
Doing the reverse without making it confusing would require a "forceFlush" (or
something like this) option in the Mutation. So we'd have writeToWal,
deferFlush, and forceFlush. Even then IMHO that would be more confusing the
helpful.
The key here is that it should possible to decide per Mutation whether to defer
or not. Without this change that is not possible. With this change it is
possible by leaving the table's default (flush) and then set the defer bit on a
Mutation.
> 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
