Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/1693
@revans2 thanks for taking the time to review.
>I really would like to see how triggers and exactly once processing might
fit into this. Not that we need it right now, but just that I would like to see
how you would fit it in, because I can see how I might do it, but I would like
to hear from others about it.
Right now the stateful operations (aggregations, join etc) uses an
in-memory map to maintain state and relies on storm's acking mechanism to
replay and rebuild the state. For exactly once we can build support at the
storm framework level (e.g. enhance the stateful bolts) so that operations like
aggregations and join can use the underlying framework state to maintain its
state. Initial ideas are here -
https://docs.google.com/document/d/1Ew7uFF1UJ6e_zq0t4bM6A9auuEaArviAjjWYSpVFqPY/edit#heading=h.nmf14n.
Anyways this needs longer discussion. Would be great if you can share your
ideas in the doc or in the JIRA https://issues.apache.org/jira/browse/STORM-2155
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
