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 8794CD321 for ; Wed, 19 Sep 2012 19:04:10 +0000 (UTC) Received: (qmail 1936 invoked by uid 500); 19 Sep 2012 19:04:08 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 1882 invoked by uid 500); 19 Sep 2012 19:04:08 -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 1621 invoked by uid 99); 19 Sep 2012 19:04:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Sep 2012 19:04:08 +0000 Date: Thu, 20 Sep 2012 06:04:08 +1100 (NCT) From: "Gregory Chanan (JIRA)" To: issues@hbase.apache.org Message-ID: <1292686962.98722.1348081448207.JavaMail.jiratomcat@arcas> In-Reply-To: <150734071.95540.1348019948004.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (HBASE-6835) HBaseAdmin.flush claims to be asynchronous but appears to be 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-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Chanan updated HBASE-6835: ---------------------------------- Fix Version/s: 0.96.0 > HBaseAdmin.flush claims to be asynchronous but appears to be synchronous > ------------------------------------------------------------------------ > > Key: HBASE-6835 > URL: https://issues.apache.org/jira/browse/HBASE-6835 > Project: HBase > Issue Type: Bug > Reporter: Gregory Chanan > Assignee: Gregory Chanan > Priority: Minor > Fix For: 0.96.0 > > > Relevant comment: > {code} > * Flush a table or an individual region. > * Asynchronous operation. > {code} > but it looks like it's synchronous. In fact, it returns whether the flush ran or not: > {code} > message FlushRegionResponse { > required uint64 lastFlushTime = 1; > optional bool flushed = 2; > } > {code} -- 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