You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 03:36:27 UTC

[jira] [Updated] (STORM-665) Lower entry barrier for understanding storm's stream management

     [ https://issues.apache.org/jira/browse/STORM-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Kellogg updated STORM-665:
-------------------------------
    Component/s: documentation

> Lower entry barrier for understanding storm's stream management
> ---------------------------------------------------------------
>
>                 Key: STORM-665
>                 URL: https://issues.apache.org/jira/browse/STORM-665
>             Project: Apache Storm
>          Issue Type: Documentation
>          Components: documentation
>            Reporter: Karl Richter
>
> Due to the fact that storm is a stream processing framework, it's necessary to explain the handling of streams in a proper documentation chapter. Currently the index at http://storm.apache.org/doc-index.html doesn't even contain the word.
> An example of missing infos includes the usage of explicit stream ids and omitting them (e.g. in `BoltDeclarer.xyGrouping`). Question which arise and are not answered: How to declare a stream (object) explicitly? Which one is used when an explicit id is omitted?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)