Can you elaborate on what exactly you mean by "join". You can have a bolt defined as part of topology which will load the other jar in the prepare() method call actual functional methods in the "execute" method. This way , you are dynamically loading the other jar into your storm topo...(which in my view... not a great idea). However, the point of concern is , how will you distribute the other jar... that's a hassle. How big is your OSGi jar and why is it such a big concern ?
Prasun On Thu, May 22, 2014 at 2:23 AM, Sajith <sajith...@gmail.com> wrote: > Hi all, > > Is it possible for us to join another spout or a bolt (not an instance, > but a separate one) later to the topology after topology being deployed. > > My requirement is to receive all the tuples processed by a storm cluster > to a single bolt which developed on OSGi and many other dependencies. I > don't want this bolt to be added to the original topology since the JAR > which contains the topology becomes bulky. > > Therefore, is it possible for me to join this special spout to the cluster > to receive messages one the toplogy is deployed. > > Any other suggestions or recommendations to achieve this are appreciated. > > Thanks, > Sajith. >
