[
https://issues.apache.org/jira/browse/STORM-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197329#comment-15197329
]
Robert Joseph Evans commented on STORM-1318:
--------------------------------------------
[~Johnbaba],
The only way I could see to make it work would be to do something like I
proposed for storm-sql
https://issues.apache.org/jira/browse/STORM-1625?focusedCommentId=15193911&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15193911
I think we can make this work if we move
{{backtype.storm.command.shell-submission}} to the {{storm-clojure}} package.
Then we have the storm-clojure jar with dependencies placed in a special
directory as part of the storm distribution, and have it play games when it
submits a topology that will try to include storm-clojure and dependencies in
the classpath for the workers.
To me that sounds like too much work to maintain compatibility so I would
propose that instead we put up two pull requests one to deprecate
shell-submission in 1.0, and another to remove it completely in 2.0. Unless
that is someone want to volunteer to do the work I outlined above.
> Investigate if backtype.storm.command.shell-submission shuld be dropped
> -----------------------------------------------------------------------
>
> Key: STORM-1318
> URL: https://issues.apache.org/jira/browse/STORM-1318
> Project: Apache Storm
> Issue Type: New Feature
> Reporter: Robert Joseph Evans
> Assignee: John Fang
> Labels: java-migration, jstorm-merger
>
> As part of the merger with Jstorm we need to decide if
> backtype.storm.command.shell-submission should be dropped, or if we should
> migrate it over to a storm-clojure package.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
