You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "James Xu (JIRA)" <ji...@apache.org> on 2013/12/15 09:10:06 UTC

[jira] [Created] (STORM-164) Split Storm into multiple modules

James Xu created STORM-164:
------------------------------

             Summary: Split Storm into multiple modules
                 Key: STORM-164
                 URL: https://issues.apache.org/jira/browse/STORM-164
             Project: Apache Storm (Incubating)
          Issue Type: Improvement
            Reporter: James Xu
            Priority: Minor


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

The preliminary work of making Storm a multimodule setup has been done (currently pretty much everything is in storm-core). The new setup is a drop-in replacement for the old setup, so the same maven artifact names still work and have the same semantics.

We have the flexibility to split Storm into smaller modules that can be included / excluded as desired by users. This makes it easier to control dependencies. Here's my current list of modules to create:

storm-ui
storm-linear-drpc
storm-drpc-server
storm-transactional-topology
storm-trident
storm-zmq-messaging
storm-client (bin/storm and related java/clojure files)

Please comment with additional modules you think Storm should be broken up into.

----------
mrflip: When you do this surgery, is it reasonable to do away with the backtype. prefix, and normalize everything onto storm. and trident. (or storm.core and storm.trident) namespaces?

Watching other folks learn the codebase (self included), it's a hurdle to keep track of where in {clj,jvm}/{backtype/storm,storm/trident} everything is.

----------
nathanmarz: That would be backwards incompatible. I'd be for that change, but as part of a future major release and independent from this issue.

----------
mrflip: sounds good, and prudent. Thanks for considering it.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)