On Wed, Mar 19, 2014 at 01:03:43PM -0700, Angelo Genovese wrote: > "Any problem in computer science can be solved with another layer of > indirection." (David Wheeler)
... and every new layer of indirection introduces new bugs, which will combine with the existings ones and produce up to N*M new problems, where N is number of bugs in the lower layer, and M - in the upper one. (Unknown Developer) > You could setup the spout to read it's list of sources from somewhere, add > to that list when a request comes in, then remove completed sources from > that list in your sink. Or you could use a separate app to read from the > sources on request and pile that info into a queue like Kestrel for a > storm spout to read from. Yes, that will probably solve the task of adding new data sources, however it's still not clear how to mark some task as "complete", so the sink could send the results back to the user. Like if the spout had produced 5 messages and 6-th is "EOT", and that EOT message arrived to sink when the message 3 was in progress. -- Eugene N Dzhurinsky
pgpYoDqXl1fe1.pgp
Description: PGP signature
