Hi.
I have a question, regarding fields grouping. In documentation we have:
```
Fields grouping: The stream is partitioned by the fields specified in the
grouping. For example, if the stream is grouped by the "user-id" field,
tuples with the same "user-id" will always go to the same task, but
Thank you.
It will be nice if documentation cover such scenarios in more clear way. :)
пт, 23 нояб. 2018 г. в 13:25, Stig Rohde Døssing :
> See
> https://github.com/apache/storm/blob/21bb1388414d373572779289edc785c7e5aa52aa/storm-client/src/jvm/org/apache/storm/daemon/GrouperFactory.java#L174
>
Ok. Thanks for confirming. I have found the "reason of concurrent
execution" in my topology and it is "outside" storm code responsibility.
Guity is lazy initialisation in some of external library.
ср, 5 июн. 2019 г. в 17:48, Stig Rohde Døssing :
> The "execute" method will never be called
Hi.
It is possible the "execute" method of the bolt to be called in "parallel"?
For example we have 3 bolts A, B and C:
topology.setBolt(BOLT_A_ID, new BoltA(), scaleFactor);
topology.setBolt(BOLT_B_ID, new BoltB(), scaleFactor);
topology.setBolt(BOLT_C_ID, new BoltC(), scaleFactor)
Hi.
I have some topology (it read messages from kafka and put results in kafka
too, maybe it matter), and time to time it fails tuples. This tuples are
reinjected in topology by spout after 60s delay for one more processing
attempt.
My question - is there any tools available that can help to
