Hi Abhishek, Storm is distributed computing framework, that means your code will be running on any of the node in your cluster. Also in a cluster you can run many Topologies.
So now when Storm move one of your topology from Node A to node B , it needs to know what all code it need to move. One jar seems the best option else you will have to provide a seprate list for your topology(exactly what single jar does). Ravi. On Thu, Jul 30, 2015 at 2:07 PM, Matthias J. Sax < [email protected]> wrote: > Storm itself does not provide any support to upload multiple jars. As a > workaround you can put required jars into $STORM/lib folder manually > (you need to do this on every node in the cluster!) > > -Matthias > > On 07/30/2015 08:55 AM, Abhishek Agarwal wrote: > > Currently, as far as I know one has to package all the dependencies into > > one jar and then submit it along with topology class. StormSubmitter > > interface also allows only one jar. Is there any particular reason for > this > > limitation? > > > > We have a use case where we want to upload more than one jar without > > packaging them together. How could this be achieved? > > > >
