Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1919
@srdo
I think it's up to the Spout implementation and we don't need to consider
ordering if we don't rely on ack() method.
If the spout is aware of the count of ackers (0 or more) and data source
provides the way to ack synchronously, nextTuple() method can have two branches
(ack vs non-ack) which handle ack/emit accordingly, and ack() method can don't
do anything when no acker is activated.
---
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.
---
