No, because Storm topologies are scheduled in isolation -- you're never going to have a topology sharing workers with another topology.
You could use Kafka, Redis, DRPC, etc. to connect them though, if you'd like. I've always been hesitant to do that though, because one topology could end up backing up and/or crashing another topology at that point. You also have the potential of over-feeding the second topology, until the buffer runs out of memory. On Thu, Jan 9, 2014 at 1:59 PM, Verma, Rishi (398J) < [email protected]> wrote: > Greetings All, > > I'm curious whether storm topologies can be "connected" together. By > connected, I mean the spouts of one topology can stream their data from the > spouts or bolts of another topology. > > The requirement here is two-fold: > 1. Be able to add complexity to a running topology, i.e. add additional > spouts and bolts that perform further processing, but while the topologies > are already running > 2. Distribute the code base of an all-encompasing topology across multiple > and separate topologies to reduce code complexity > > One possible solution is to just push the outputs of a topology to a > message broker, and have a second topology stream data from the broker > directly. However, I'm looking to see whether Storm has some built-in > support for connecting the nodes and spouts of separate topologies together. > > Thank you! > Rishi
