hi Richard

As I know, tuple.getMessageId().toString() should be unique. If you get a
hashCode of 0, it means that your messageid is empty. It may be that you
disabled ack of the topology.


On Sun, Jul 13, 2014 at 7:16 PM, Richard Burkhardt <[email protected]>
wrote:

> I realized that storms tuple do not have a unique id inside bolt (I logged
> it in a cluster). The tuple.MessageId.hashCode only returns 0. Is there
> another way to receive the unique id?
>
> The ShellBolt generates an extra unique id for each tuple (
> https://github.com/apache/incubator-storm/blob/master/
> storm-core/src/jvm/backtype/storm/task/ShellBolt.java#L171)
>
> The executor seems to already create a unique id for the MessageId (
> https://github.com/apache/incubator-storm/blob/
> 79f258ec6d3e85f190a7e4861ff6cefb1ce905f4/storm-core/src/clj/
> backtype/storm/daemon/executor.clj#L424)
>
> Am I doing something wrong?
>



-- 
Best Regards!

肖康(Kang Xiao,<[email protected]>)
Distributed Software Engineer

Reply via email to