Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B0D6610106 for ; Tue, 20 Aug 2013 00:04:53 +0000 (UTC) Received: (qmail 54903 invoked by uid 500); 20 Aug 2013 00:04:52 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 54830 invoked by uid 500); 20 Aug 2013 00:04:52 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 54772 invoked by uid 99); 20 Aug 2013 00:04:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 00:04:52 +0000 Date: Tue, 20 Aug 2013 00:04:52 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-9266) Javadoc: Document that HBaseAdmin.flush(...) is synchronous 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-9266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Hofhansl resolved HBASE-9266. ---------------------------------- Resolution: Fixed Hadoop Flags: Reviewed Committed to 0.94 (in 0.95+ already) > Javadoc: Document that HBaseAdmin.flush(...) is synchronous > ----------------------------------------------------------- > > Key: HBASE-9266 > URL: https://issues.apache.org/jira/browse/HBASE-9266 > Project: HBase > Issue Type: Bug > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Priority: Trivial > Fix For: 0.94.12 > > Attachments: 9266.txt > > > Currently the Javadoc in HBaseAdmin.flush(...) says that this is an asynchronous operation. Looking at the, however, it is in fact not. > Having this as a synchronous operation open ups some use cases we're interested in. For example doing some ingest via the high level API with WAL disabled and then issue a flush through the HBaseAdmin. When the flush succeeded we know the data is securely in HBase. > (This should work even with intermediary splits, as they also force a flush, but that needs to be verified as well. > So this is just for a trivial Javadoc change. -- 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