https://github.com/nathanmarz/storm

Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more
https://github.com/nathanmarz/storm

Last synced: 27 days ago
JSON representation

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

• Host: GitHub
• URL: https://github.com/nathanmarz/storm
• Owner: nathanmarz
• License: apache-2.0
• Created: 2011-09-17T07:55:13.000Z (about 13 years ago)
• Default Branch: moved-to-apache
• Last Pushed: 2017-08-16T04:24:20.000Z (about 7 years ago)
• Last Synced: 2024-09-08T10:56:44.516Z (2 months ago)
• Language: Java
• Homepage: http://storm-project.net
• Size: 25.8 MB
• Stars: 8,839
• Watchers: 1,028
• Forks: 1,665
• Open Issues: 42
• Metadata Files:
  • Readme: README.markdown
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-github-repos - nathanmarz/storm - Distributed and fault-tolerant realtime computation: stream processing, continuous computation, distributed RPC, and more (Java)

README

        
## 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](https://github.com/apache/incubator-storm)

### Contributing

Source code contributions can be submitted either by [sumitting a pull request](https://github.com/apache/incubator-storm/pulls) or by creating an issue in [JIRA](https://issues.apache.org/jira/browse/STORM) 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](https://issues.apache.org/jira/browse/STORM)

### User Mailing List

Storm users should send messages and subscribe to [[email protected]](mailto:[email protected]).

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

You can view the archives of the mailing list [here](http://mail-archives.apache.org/mod_mbox/incubator-storm-user/).

### Developer Mailing List

Storm developers should send messages and subscribe to [[email protected]](mailto:[email protected]).

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

You can view the archives of the mailing list [here](http://mail-archives.apache.org/mod_mbox/incubator-storm-dev/).

### 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]]([email protected]). 

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

### What will happen with [email protected]?

All existing messages will remain archived there, and can be accessed/searched [here](https://groups.google.com/forum/#!forum/storm-user).

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.