hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9266) Javadoc: Document that HBaseAdmin.flush(...) is synchronous
Date Mon, 19 Aug 2013 23:36:51 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13744513#comment-13744513

Lars Hofhansl commented on HBASE-9266:

Ah, didn't know about HBASE-6835. Will just "backport" that then. In the future we can always
add a asyncFlush when needed.

> 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.98.0, 0.94.12, 0.95.3
> 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

View raw message