[
https://issues.apache.org/jira/browse/STORM-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933345#comment-14933345
]
Robert Joseph Evans commented on STORM-1070:
--------------------------------------------
[~rkellogg]
We now have the following
documentation: Storm documentation and the website
storm-slor: Storm Slor Integration
storm-jdbc: Storm JDBC Integration
storm-hive: Strom Hive Integration
storm-multilang: Storm integration with other programming languages
storm-core: Core storm daemons and APIs including trident
external
Flux: Flux
storm-eventhubs: MS Azure Event Hubs Integration
storm-hbase: Storm HBase Integration
storm-hdfs: Storm HDFS Integration
storm-kafka: Storm Kafka Integration
storm-redis: Storm Redis integration
examples: Storm-starter and other examples
I would like to remove external once you finish updating the JIRA to point to
the correct component. I didn't add in storm-nimbus, storm-supervisor,
storm-drpc, or storm-ui, as I felt they were redundant with storm-core. But if
you really want them I can add them in.
> Additional JIRA Components
> --------------------------
>
> Key: STORM-1070
> URL: https://issues.apache.org/jira/browse/STORM-1070
> Project: Apache Storm
> Issue Type: Task
> Reporter: Rick Kellogg
> Assignee: Robert Joseph Evans
> Priority: Minor
>
> Create additional JIRA components in Storm project:
> storm-core
> storm-multilang
> storm-nimbus
> storm-supervisor
> storm-drpc
> storm-elasticsearch
> storm-hive
> storm-jdbc
> storm-solr
> storm-examples (for storm-starter and others)
> storm-ui
> For consideration:
> documentation
> build
> website
> security
> Would also consider making component required when creating new bugs.
> Default would be storm-core.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
