Jayesh created EAGLE-939:
----------------------------
Summary: individualize app jars for eagle
Key: EAGLE-939
URL: https://issues.apache.org/jira/browse/EAGLE-939
Project: Eagle
Issue Type: Improvement
Affects Versions: v0.6.0
Reporter: Jayesh
Assignee: Jayesh
Fix For: v0.6.0
currently eagle packages everythnig into 1 fat topology jar which it uses to
submit to storm to distribute to the workers. there are couple of pros and cons
with this approach.
1) user can not develop app outside of eagle and use the packaged jar to run
the app on eagle, instead user has to develop app within eagle code base or
update eagle parent Pom.xml to add that app as module to get the app jar
included into topology.
2) topology jar has to be repakaged everytime there is a app level changes
3) each app worker will be holding jar that has all the apps but only use 1 app
classes
looks like there is a limitation for submitting storm topology where it only
takes 1 jar, this needs to be investigated further, since based on this ticket
storm may have added support for multiple jar lately. (ref: STORM-2016)
Also after eagle 0.5, there is a plan to move on storm 1.x which will enable us
to leverage the multi jar functionality of storm. ( ref: EAGLE-906)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
