[STORM-129] Keep Storm dependencies and user dependencies independent

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: storm-core
• Labels: HighPriority
• Assignee: Unassigned
• Reporter: James Xu
• Created: 15/Dec/13 05:00
• Updated: 09/Oct/15 00:16

Description

https://github.com/nathanmarz/storm/issues/115

For instance, user classes should be able to use a different version of a library than Storm uses. Users have run into issues with Hibernate since Hibernate requires asm 1.4 while Storm requires asm 3.3 (through Kryo).

This is tricky since the Storm code and user code run together. e.g., when a user does an emit call, that calls into Storm code which calls into Kryo, 0mq, etc. It's not clear how to keep the dependencies separate.

Possible technologies to look at include OSGi and JPF. However, there is a serious concern about the complexity and overhead of these approaches.

Hadoop has the exact same problem, so it's worth looking to see if it does anything to address this. AFAIK, it doesn't.

Issue Links

• is related to: SAMZA-305 Isolate user library dependencies from framework dependencies