Github user srdo commented on the issue:
https://github.com/apache/storm/pull/1924
@HeartSaVioR I agree, I think it would be much simpler to rely on
maxSpoutPending. maxUncommittedOffsets does have a slightly different meaning
though. With only maxSpoutPending, the spout might progress arbitrarily far
past the last committed offset, since there's only a limit on how many tuples
are in-flight at once, rather than on how many tuples have been emitted past
the committed offset. If a user needs to cap how far the spout can read ahead
for some reason, they can't do that with maxSpoutPending.
I can't tell if that's a real need anyone has though. @hmcl any opinion?
---
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.
---
