Repository: storm Updated Branches: refs/heads/master 413389973 -> 68d3a5a35
Fix docs incorrect number of stream groupings Project: http://git-wip-us.apache.org/repos/asf/storm/repo Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/f1703767 Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/f1703767 Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/f1703767 Branch: refs/heads/master Commit: f1703767e1112cd51c48b53b65889d3b7cf14f59 Parents: 4133899 Author: Xin Wang <[email protected]> Authored: Thu Jul 16 11:26:39 2015 +0800 Committer: Xin Wang <[email protected]> Committed: Thu Jul 16 11:26:39 2015 +0800 ---------------------------------------------------------------------- docs/documentation/Concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/storm/blob/f1703767/docs/documentation/Concepts.md ---------------------------------------------------------------------- diff --git a/docs/documentation/Concepts.md b/docs/documentation/Concepts.md index 852c1e9..bd7ed3d 100644 --- a/docs/documentation/Concepts.md +++ b/docs/documentation/Concepts.md @@ -80,7 +80,7 @@ Please note that [OutputCollector](/javadoc/apidocs/backtype/storm/task/OutputCo Part of defining a topology is specifying for each bolt which streams it should receive as input. A stream grouping defines how that stream should be partitioned among the bolt's tasks. -There are seven built-in stream groupings in Storm, and you can implement a custom stream grouping by implementing the [CustomStreamGrouping](/javadoc/apidocs/backtype/storm/grouping/CustomStreamGrouping.html) interface: +There are eight built-in stream groupings in Storm, and you can implement a custom stream grouping by implementing the [CustomStreamGrouping](/javadoc/apidocs/backtype/storm/grouping/CustomStreamGrouping.html) interface: 1. **Shuffle grouping**: Tuples are randomly distributed across the bolt's tasks in a way such that each bolt is guaranteed to get an equal number of tuples. 2. **Fields grouping**: The stream is partitioned by the fields specified in the grouping. For example, if the stream is grouped by the "user-id" field, tuples with the same "user-id" will always go to the same task, but tuples with different "user-id"'s may go to different tasks.
