Dependency relocation/shading

[Drew Goya <dr...@gradientx.com>]

Hey all,  I've been running into a problem lately and I'm guessing a few of
you have as well.

As the apps we run on storm get more complex our list of dependencies has
grown pretty large.  To keep everything sane I've been digging through the
dependency tree and marking everything in the storm lib dir as provided and
locking the version.  This works most of the time but takes a lot of time
and is very error prone.  Moving between storm versions is really tricky as
this dependency shuffle has to happen all over again.

I know the team has decided to relocate/shade a few key dependencies to
prevent these collisions and give storm users more flexibility.  Have you
guys tossed around the idea of relocating/shading every storm dependency?
So the only jar in lib is the storm uber jar with no possible dependency
collision?

Re: Dependency relocation/shading

[Jeremy Heiler <je...@gmail.com>]

There are various discussions that talk about classloader isolation. I feel
like this would be the most ideal solution, but I haven't investigated it.

https://issues.apache.org/jira/browse/STORM-129