Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 12 Feb 2013 23:51:13 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12631569.1360392398887.281293.1360713073709@arcas>
In-Reply-To: <JIRA.12631569.1360392398887@arcas>
References: <JIRA.12631569.1360392398887@arcas>
Subject: [jira] [Updated] (HBASE-7801) Allow a deferred sync option per
 Mutation.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-7801:
---------------------------------

    Attachment: 7801-0.94.txt

Here's a surprisingly simple work in progress patch for 0.94.
This is back and forward compatible between old clients and new servers or vice version.

Note: COMPLETELY UNTESTED.

                
> 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
>             Fix For: 0.96.0, 0.94.6
>
>         Attachments: 7801-0.94.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