[
https://issues.apache.org/jira/browse/STORM-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320403#comment-14320403
]
Zachary Roadhouse commented on STORM-129:
-----------------------------------------
This is a problem for us since we'd like to include 3rd party tools like the
AWS Java SDK which require libraries that are newer than what are included by
Storm.
> Keep Storm dependencies and user dependencies independent
> ---------------------------------------------------------
>
> Key: STORM-129
> URL: https://issues.apache.org/jira/browse/STORM-129
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: James Xu
> Labels: HighPriority
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
