[STORM-206] Incorporate "Contrib" Modules into Apache Build and Release Process

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Component/s: storm-core
• Assignee: Unassigned
• Reporter: P. Taylor Goetz
• Created: 29/Jan/14 17:32
• Updated: 02/Jul/24 09:54
• Resolved: 02/Jul/24 09:54

Description

It would be nice to have some sort of process for including optional Storm components (Kafka Spout, etc.) in the Storm build and release process.

This would make it easier to keep such components version-aligned with the main Storm build and potentially reduce fragmentation (like that which occurred with the Kafka Spout).

We will need to figure out how such modules will be incorporated into the project/build, as well as a process for adding and maintaining modules.

Some existing modules might need to go through the IP clearance process before being included, so we'll need some process around that as well.

Sub-Tasks

• Add storm-starter as a module: Resolved
• Add storm-kafka as a module: Resolved
• Add storm-cassandra as a module: Closed
• Add storm-hbase module: Resolved
• Add module for HDFS integration: Resolved
• Add storm-jms as a module: Closed