Hi,

I am building a topology, in which it first needs to read some persisted data 
(accounts, recovery point, etc) before all the bolts can start processing 
tuples.


Ideally the spout starts to emit tuples only after all the required data is 
read into memory (maybe on spouts, maybe on bolts). What’s the general approach 
to deal with such use case?


Alternatively I can make each bolt to ignore/fail tuples until it’s ready to 
process, but that means either loss of message or futile spout replays.


Thanks,
Jia





-Jia

Reply via email to