Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/772#issuecomment-145210986
I missed something before voting: seems like we should think about meaning
about default values.
If user takes default configuration, tuples could be timed out on low
throughput bolt because default will be changed to use batch but don't set tick
tuple for flushing.
(Please note that default value of flushIntervalSecs is 0)
It breaks backward compatibility, and since Storm should also consider low
latency requirement, I think there's no reason to change to use batch by
default.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
