Our strategy: Use BaseRichBolt
fail retriable exceptions catch and report non retriable ones. then ack the tuple but emit nothing. That's it. End of the line for that tuple. Think of it this way... fail means "retry" ack means "i'm done with this" On Thu, Feb 27, 2014 at 5:23 AM, Harald Kirsch <[email protected]>wrote: > Hi all, > > a tuple can fail for different reasons, some may be temporary, for example > a timeout due to high load, some may be permanent, for example a > NullPointerException. > > Is there a way for a Spout to get any information back as to why a tuple > failed in order to make an informed decision of whether it makes sense to > send the tuple again or not? > > Thanks, > Harald. > -- Ce n'est pas une signature
