Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3C353D75E for ; Fri, 22 Feb 2013 00:10:15 +0000 (UTC) Received: (qmail 6048 invoked by uid 500); 22 Feb 2013 00:10:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 6005 invoked by uid 500); 22 Feb 2013 00:10:14 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 5947 invoked by uid 99); 22 Feb 2013 00:10:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2013 00:10:14 +0000 Date: Fri, 22 Feb 2013 00:10:14 +0000 (UTC) From: "Sergey Shelukhin (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-7801) Allow a deferred sync option per Mutation. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583711#comment-13583711 ] Sergey Shelukhin commented on HBASE-7801: ----------------------------------------- {code} + } else if (!shouldSyncWal) { + shouldSyncWal |= !m.getDeferWALFlush(); {code} |= is not necessary. > 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