Skip to content
/ storm Public
forked from nathanmarz/storm

Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more

License

Notifications You must be signed in to change notification settings

Dora1984/storm

 
 

Repository files navigation

IMPORTANT NOTE!!!

Storm has Moved to Apache. The official Storm git repository is now hosted by Apache, and is mirrored on github here:

https://github.com/apache/incubator-storm

Contributing

Source code contributions can be submitted either by sumitting a pull request or by creating an issue in JIRA and attaching patches.

Migrating Git Repos from nathanmarz/storm to apache/incubator-storm

If you have an existing fork/clone of nathanmarz/storm, you can migrate to apache/incubator-storm by doing the following:

  1. Create a new fork of apache/incubator-storm

  2. Point your existing clone to the new fork:

     git remote remove origin
     git remote add origin [email protected]:username/incubator-storm.git
    

Issue Tracking

The official issue tracker for Storm is Apache JIRA:

https://issues.apache.org/jira/browse/STORM

User Mailing List

Storm users should send messages and subscribe to [email protected].

You can subscribe to this list by sending an email to [email protected]. Likewise, you can cancel a subscription by sending an email to [email protected].

You can view the archives of the mailing list here.

Developer Mailing List

Storm developers should send messages and subscribe to [email protected].

You can subscribe to this list by sending an email to [email protected]. Likewise, you can cancel a subscription by sending an email to [email protected].

You can view the archives of the mailing list here.

Which list should I send/subscribe to?

If you are using a pre-built binary distribution of Storm, then chances are you should send questions, comments, storm-related announcements, etc. to [email protected].

If you are building storm from source, developing new features, or otherwise hacking storm source code, then [email protected] is more appropriate.

What will happen with [email protected]?

All existing messages will remain archived there, and can be accessed/searched here.

New messages sent to [email protected] will either be rejected/bounced or replied to with a message to direct the email to the appropriate Apache-hosted group.

About

Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Java 75.1%
  • Clojure 21.5%
  • CSS 1.4%
  • Python 1.1%
  • Thrift 0.3%
  • Shell 0.2%
  • Other 0.4%