Hi, The questions are around sequencing and synchronization of certain tuples.
In my use case, I have a few spouts that act upon millions of cached rows before the updated rows successfully exit the topology (published to clients). A new tuple (an update) from spout A may result in thousands of updated rows. The same with spout B, except that the updates may or may not overlap. Also, performance is important. The questions are: 1. How can I ensure the updates for each row is applied in the order of arrival? (As a given row can be updated from multiple spouts/streams) 2. How can I ensure a new update does not step over in-flight updates? (Probably the same as the last question) Thank you << �gA mind is like a parachute. It doesn't work if it is not open.�h Frank Zappa >>
