[
https://issues.apache.org/jira/browse/STORM-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089597#comment-15089597
]
ASF GitHub Bot commented on STORM-1202:
---------------------------------------
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/889#issuecomment-170073038
* Downloaded 0.11 source & pulled in this branch
* ran the move_packages.sh, build and unpacked the tarball
* launched daemons from the unpacked 0.11+hack build
* downloaded 0.10 release tarball and unpacked it separately
* Used the 0.11+hack bin/storm to launch the 0.10
storm.starter.clj.word_count
* -> Client failed because of missing StormSubmitter package
(good/expected)
* Did the same adding `-c
client.jartransformer.class=org.apache.storm.hack.StormShadeTransformer`
* -> topology submitted and ran OK
* Checked the stormjar.jar in the supervisor's stormdist directory and
looked at the word_count.clj source file inside it, and the source had been
rewritten from backtype.storm.... to org.apache.storm...
The one suggestion is to add to Config what the hack implementation class
is (the intended value of the config) for the use case. Otherwise users might
need to hunt around to find the class we provide.
Once that's added, +1
> Migrate APIs to org.apache.storm, but try to provide backwards compatability
> as a bridge
> ----------------------------------------------------------------------------------------
>
> Key: STORM-1202
> URL: https://issues.apache.org/jira/browse/STORM-1202
> Project: Apache Storm
> Issue Type: New Feature
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> We want to move the storm classpaths to org.apache.storm wherever possible,
> but we also want to provide backwards compatibility for user facing APIs
> whenever possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
