If resend is achieved by transactional topology, transaction attempt argument can indicate whether tuples is resent or not. It contains two fields, transaction ID and attempt, which means retrying times.
If non-transactional topology is used, I don't think storm provides any way to indicate that directly unless you implement it yourself. Cheers, Matt 发自我的 iPad > 在 2014年1月17日，4:11，Adrian Mocanu <[email protected]> 写道： > > Hi group, > Say I’m doing a moving average on real time data from storm. > I am interested in dealing with failed tuples. > > If I can’t save the average to the db (for whatever reason), the tuple is > failed which in turn makes storm re send it. The moving average bolt needs to > somehow know if a tuple is a resend or a new one so that if it’s a resend it > doesn’t try to add it to the average (it being already part of the average). > Is there a parameter in tuple that tells if the tuple is a resend or a new > one? > > Thanks > -Adrian >
