[
https://issues.apache.org/jira/browse/FLUME-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288306#comment-13288306
]
Hari Shreedharan commented on FLUME-1252:
-----------------------------------------
Thanks Otis. I will take a look at asynchbase. What I meant to ask was how
asynch callbacks will work with our current txn model. Right now, we have
single threaded sinks which sit in a loop, and commit transactions. Each txn is
committed only once we know all events from that txn are persisted by the next
hop or by the storage system. If we use asynchronous writes to hbase, we still
cannot commit a transaction without waiting for the callbacks.
Since our channels do not support more than one transaction at a time, I do not
see any benefit of making the writes asynchronous(unless of course, asynchbase
some how performs better than the hbase client API/htable API and the writes
complete faster).
> Asynchronous HBase Sink
> -----------------------
>
> Key: FLUME-1252
> URL: https://issues.apache.org/jira/browse/FLUME-1252
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Reporter: Otis Gospodnetic
> Fix For: v1.2.0
>
>
> The current HBase sink is synchronous/blocking. Asynchbase HBase client
> outperforms HTable. It would be nice to have an HBase sink that uses
> asynchbase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
