For an end user submitting topologies manually, it is probably easier to just upload one uber jar. However, we have a system in place where a client can come and submit the code which will run alongside the system code. In such case, this system would like to spawn a storm topology and run the client jar and the system jar. That is not possible right now.
Also there should not be any dependency conflicts across the topologies, be it single jar or multiple jars. If the topology is moved to another node, supervisor should download all the jars just like it downloads the uber jar. On Fri, Jul 31, 2015 at 7:52 PM, Harsha <[email protected]> wrote: > Abhishek, > Can you explain whats your use case and the need for uploading > multiple jars without packaging together. As others have noted since storm > expected to have multiple topologies in ordered to prevent dependency > conflicts across the topologies its better to submit one jar with all of > its dependencies included in the jar. > > Thanks, > Harsha > > > On July 29, 2015 at 11:57:19 PM, Abhishek Agarwal ([email protected]) > 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? > > -- > Regards, > Abhishek Agarwal > > -- Regards, Abhishek Agarwal
