Details
-
Bug
-
Status: Done
-
Major
-
Resolution: Done
-
0.3.0
-
None
Description
The ProfileBuilderBolt incorrectly assumes that it will only ever see a single [profile, entity] pair. The bolt maintains a single StellarExecutor that is responsible for executing the init, update, result expressions. This assumption is incorrect as Storm's field grouping only guarantees that the same profile/entity pairs will go to the same task. Storm does not guarantee that a task only receives a single profile/entity pair.
The easiest fix is to maintain a cache that maps a profile/entity to its state. This would follow what is currently done in the Join bolt.
Attachments
Issue Links
- links to
