Re: [storm-user] Upgrade Storm HttpClient Version

305 views
Skip to first unread message

Krishna Gade

unread,
May 18, 2013, 6:59:37 PM5/18/13
to storm...@googlegroups.com
dependency exclusion does not work?

-- Krishna
@krishnagade


On Fri, May 17, 2013 at 2:39 PM, Jamie Johnson <jej...@gmail.com> wrote:
> I am using a library that requires a later version of httpclient then what
> is shipped with Storm (specifically 4.3). What is the most appropriate way
> to move to this new version? Is anyone aware of conflicts if we modify
> storm to use this? Are there any other ways that we can do this without
> modifying storms default libraries? Any help is appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "storm-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to storm-user+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Jamie Johnson

unread,
May 19, 2013, 5:14:04 PM5/19/13
to storm...@googlegroups.com
If I exclude the dependency from the required library it will fail to work.  I was wondering if anyone had any experience with using a later version of HttpClient with Storm since it is present in the /lib folder that storm uses.  I plan to just drop the later version in and see if it works but I was hoping someone would have some experience with this and any issues I may run into.

NerdyNick

unread,
May 20, 2013, 11:43:43 AM5/20/13
to storm...@googlegroups.com
We had the same problem and excluded storms version in favor of the 4.3 version. Storm has been working just fine since. Granted this is currently only in our dev/qa env. 
--
Nick Verbeck - NerdyNick
----------------------------------------------------
NerdyNick.com
Coloco.ubuntu-rocks.org

Jamie Johnson

unread,
May 20, 2013, 4:14:04 PM5/20/13
to storm...@googlegroups.com
Thanks Nick.  I'll go ahead and give that a whirl.

NerdyNick

unread,
May 20, 2013, 4:31:06 PM5/20/13
to storm...@googlegroups.com
The only thing I can think of that might crop up is that the classpath builder in the storm launcher might try to put the storm version, in lib folder, in front of your uber jar. So a solution might be to just swap that version as well.

But let me know how it goes. We haven't full tested trying this on our own.

JF Picard

unread,
May 21, 2013, 9:25:40 AM5/21/13
to storm...@googlegroups.com
We sucessfully replaced the http*.jar in the lib folder of storm by a new version without any problems.

You might do that with all the storm installation on the cluster.

NerdyNick

unread,
May 21, 2013, 10:47:41 AM5/21/13
to storm...@googlegroups.com
Question also becomes is the http dependency only used for the WebUI or used through out. If just the WebUI will the splitting of the code base up maybe help resolve this issue in the future, or should a bug report be filed to update this for a future release?
Reply all
Reply to author
Forward
0 new messages