Resending... Our use case requires the tuples be processed in order across failures.
So we have SpoutA sending data to bolt B &C and Bolt D is the last bolt that aggregates data from B & C and writes to a database. We want to make sure that when we use tuple at a time processing OR use the Trident API, the data always gets processed in the same order as it was read by our spout. Given that between Bolt B & C there would be parallelism and intermittent failures, my question is the following - How does Storm guarantee processing order of tuples? Thanks in advance! On Wed, Jan 21, 2015 at 10:57 AM, Shawn Bonnin <[email protected]> wrote: > Our use case requires the tuples be processed in order across failures. > > So we have SpoutA sending data to bolt B &C and Bolt D is the last bolt > that aggregates data from B & C and writes to a database. > > We want to make sure that when we use tuple at a time processing OR use > the Trident API, the data always gets processed in the same order as it was > read by our spout. Given that between Bolt B & C there would be parallelism > and intermittent failures, my question is the following - > > How does Storm guarantee processing order of tuples? > > Thanks in advance! > > >
