[
https://issues.apache.org/jira/browse/HBASE-6835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459221#comment-13459221
]
Hudson commented on HBASE-6835:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #182 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/182/])
HBASE-6835 HBaseAdmin.flush claims to be asynchronous but appears to be
synchronous (Revision 1387745)
Result = FAILURE
gchanan :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java
> 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
>
> Attachments: HBASE-6835.patch
>
>
> 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