Generally, in streams processing frameworks the general rule of thumb is to try to keep the thread management to the framework but you can certainly have your own TimerTask or a different thread in your spout that's scheduling when to do things.
Of course, if you emit something on the timer without honoring the nextTuple() method in the spout then you could blow the heap and cause unexpected results (as you are not allowing Storm's flow control to kick in). An excepted way of implementing tuples in a timer is to queue them up yourself and have the nextTuple() method pull from your own queue. On Tue, Oct 7, 2014 at 5:43 AM, 이승진 <[email protected]> wrote: > Dear all, > > > > I know there is a tick tuple component which makes it possible to do > certain job periodically within bolts. > > > > To my knowledge however, it seems like spouts cannot receive a tick tuple > since there's no argument in nextTuple method. > > (BaseRichSpout) > > > > Is there any other option to implement cron-like job within a spout? Any > comment will help. > > Sincerely, > >
