Github user mmiklavc commented on the issue:
https://github.com/apache/incubator-metron/pull/188
It is a much simpler design and it leverages Storm's built-in mechanisms
for performing actions like DB flushes. Also, you don't have to worry about
multi-threading in your bolt if you want to flush prior to your buffer being
full when you haven't received a tuple in a while. e.g. I have 99 tuples and
need 100 for a flush, but don't receive a tuple for n minutes - without using
tick tuples, you either just sit and wait, add a thread that needs to check
internally, or add another external bolt with a clock.
I'm not aware of any cons to using the TT approach. This is what tick
tuples were built for.
---
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.
---
