tree: 6cb9c2e7bf5c9517639936ef24509161fbce620e [path history] [tgz]
  1. flux/
  2. sql/
  3. storm-autocreds/
  4. storm-cassandra/
  5. storm-druid/
  6. storm-elasticsearch/
  7. storm-eventhubs/
  8. storm-hbase/
  9. storm-hdfs/
  10. storm-hive/
  11. storm-jdbc/
  12. storm-jms/
  13. storm-kafka/
  14. storm-kafka-client/
  15. storm-kafka-migration/
  16. storm-kafka-monitor/
  17. storm-kinesis/
  18. storm-metrics/
  19. storm-mongodb/
  20. storm-mqtt/
  21. storm-opentsdb/
  22. storm-pmml/
  23. storm-redis/
  24. storm-solr/
  25. storm-submit-tools/

About Storm External Modules

##What is “external”? “external” is a group of modules that while not required for storm to operate, are useful for extending Storm in order to provide additional functionality such as integration with other technologies frequently used in combination with Storm.

External modules are released in tandem with Storm in order to maintain version compatibility.

Each external module is assigned one or more “Committer Sponsors” who have expressed interest in supporting the module.

##What is a Committer Sponsor? A Committer Sponsor is simply an Apache Storm Committer who has expressed interest in supporting a module in one way or another. For any given module, we hope to have at least one sponsor to provide some level of protection against code rot and abandonware.

Note that this in no way implies that Committer Sponsors have any special roles, privileges, or obligations. The Apache Storm Committers have equal authority over and responsibility for the entire codebase. A Committer Sponsor is essentially just a Committer who has said: “I'm interested in this module, and am willing to help where I can.”