[
https://issues.apache.org/jira/browse/HBASE-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578926#comment-13578926
]
Anoop Sam John commented on HBASE-7801:
---------------------------------------
[~lhofhansl] Thanks for sharing the use case.
So we can say
1. When for a table most of the Mutations need WAL write flush immediately and
very few can come with defer flush, we will not set the table defer flush but
those Mutations to be defer flush
2. When for a table most of the Mutations can be defer flushed and few must be
immediately flushed, we will not set table defer. On majority of the Mutations
we will set defer flush attribute. Those which need immediate flush, we wont
set the defer attribute.
3. When all the Mutations on a table can go with defer flush, set the table
defer flush attribute and no other change is needed.
Just saying as a conclusion. If most of the use case will be like #1, then I am
fine Lars. :) BTW looked at the patch. Looks fine with me otherwise.
> 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
