No, it doesn't have to be. You're in full control of it. Internally Storm generates its own tuple ID and maintains a map from that globally unique tuple id to your spout id. The spout id is simply used in the ack/fail methods of the spout (so that you know what was acked/failed)
On Tue, Mar 18, 2014 at 6:01 PM, Srinath C <[email protected]> wrote: > Hi, > I was unable to figure out if the messageId of a tuple emitted from a > spout should be globally unique? Or does storm identify a tuple with a > combination of spout name, spout task Id and messageId? > > Thanks, > Srinath. > > -- Twitter: @nathanmarz http://nathanmarz.com
