You might want to check out Storm Signals.
https://github.com/ptgoetz/storm-signals
It might give you what you're looking for.
On Sat, May 7, 2016, 11:59 AM Matthias J. Sax wrote:
> As you mentioned already: Storm is designed to run topologies forever ;)
> If you have finite data, why do you no
If you need something to be done at a regular interval within Storm you
might wanna leverage the "tick tuple" concept:
- http://kitmenke.com/blog/2014/08/04/tick-tuples-within-storm/
On Fri, May 6, 2016 at 11:53 PM, Daniela S wrote:
> Hi,
>
> I would like to use Redis as a kind of cache for
I am not sure, but I guess the tuple will fail and the ack will be ignored.
-Matthias
On 05/06/2016 10:27 AM, Matthew Lowe wrote:
> If you fail a tuple then ack it immediately afterward, what happens? Is this
> bad? Can this cause problems?
>
> Best Regards
>
signature.asc
Description: Ope
As you mentioned already: Storm is designed to run topologies forever ;)
If you have finite data, why do you not use a batch processor???
As a workaround, you can embed "control messages" in your stream (or use
an additional stream for them).
If you want a topology to shut down itself, you could
