[
https://issues.apache.org/jira/browse/FLUME-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291953#comment-15291953
]
Abraham Fine commented on FLUME-2910:
-------------------------------------
Looking at the javadocs for stumbleupon's async (which asynchbase uses) here:
http://www.stumbleupon.com/su/19ESrH/tsunanet.net/~tsuna/async/api/
{quote}
When the current result of a Deferred is an instance of Exception, the next
errback is invoked. As for normal callbacks, whatever the errback returns
becomes the current result. If the current result is still an instance of
Exception, the next errback is invoked. If the current result is no longer an
Exception, the next callback is invoked.
{quote}
The code that calls the callback is a little clearer
(https://github.com/OpenTSDB/async/blob/v1.4.0/src/Deferred.java#L688,
https://github.com/OpenTSDB/async/blob/v1.4.0/src/Deferred.java#L1257):
{code:java}
doCall(result instanceof Exception ? eb : cb)
{code}
where eb is the "errback" and cb is the normal callback.
> AsyncHBaseSink - Failure callbacks should log the exception that caused them
> ----------------------------------------------------------------------------
>
> Key: FLUME-2910
> URL: https://issues.apache.org/jira/browse/FLUME-2910
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.6.0
> Reporter: Abraham Fine
> Assignee: Abraham Fine
> Attachments: FLUME-2910.patch
>
>
> Failure callbacks in the AsyncHBaseSink currently do not log the exception
> that causes them to be called, this should be fixed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
