You need to exclude storm-core from your uber jar. On Wed, Mar 30, 2016 at 11:51 AM, Erik Weathers <[email protected]> wrote:
> Can you please be more specific? i.e., which jars are considered > duplicate? Can you provide a stack trace? > What version of storm are you using? There have been a lot of changes > regarding storm-core's shading of internal dependencies. > > - Erik > > On Tue, Mar 29, 2016 at 10:34 PM, Vineet Mishra <[email protected]> > wrote: > >> Hi Sai and All, >> >> What I meant by duplicate issue was that while running the jar through >> StormSubmitter (which was build through maven) I got duplicate jars present >> for the Storm which was failing at the job submission. >> >> Any workaround or standard practice to avoid the same. >> >> Thanks! >> VM >> On Mar 30, 2016 9:43 AM, "Sai Dilip Reddy Kiralam" < >> [email protected]> wrote: >> >>> Hi vineet, >>> >>> If I understand you correctly your saying that ' when you submitted the >>> topology you noticed that your kafka spout is getting some duplicates and >>> sending it storm topology for processing'. Right? >>> >>> >>> *Best regards,* >>> *K.Sai Dilip Reddy,* >>> >>> >>> >>>> >>> > -- Regards, Abhishek Agarwal
