SAMZA-858 : Minor documentation fixes
Project: http://git-wip-us.apache.org/repos/asf/samza/repo Commit: http://git-wip-us.apache.org/repos/asf/samza/commit/95ba041b Tree: http://git-wip-us.apache.org/repos/asf/samza/tree/95ba041b Diff: http://git-wip-us.apache.org/repos/asf/samza/diff/95ba041b Branch: refs/heads/samza-sql Commit: 95ba041bc493769230e3171d95f5b2ab9da68442 Parents: 868cff7 Author: Navina <[email protected]> Authored: Tue Jan 19 12:12:02 2016 -0800 Committer: Navina <[email protected]> Committed: Tue Jan 19 12:12:02 2016 -0800 ---------------------------------------------------------------------- docs/learn/documentation/versioned/container/samza-container.md | 2 +- docs/learn/documentation/versioned/introduction/concepts.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/samza/blob/95ba041b/docs/learn/documentation/versioned/container/samza-container.md ---------------------------------------------------------------------- diff --git a/docs/learn/documentation/versioned/container/samza-container.md b/docs/learn/documentation/versioned/container/samza-container.md index a7236a6..55bec98 100644 --- a/docs/learn/documentation/versioned/container/samza-container.md +++ b/docs/learn/documentation/versioned/container/samza-container.md @@ -107,7 +107,7 @@ There is one caveat in all of this: Samza currently assumes that a stream's part After 0.10.0, Samza supports broadcast streams. You can assign partitions from some streams to all the tasks. For example, you want all the tasks can consume partition 0 and 1 from a stream called global-stream-1, and partition 2 from a stream called global-stream-2. You now can configure: {% highlight jproperties %} -task.broadcast.inputs=yourSystem.broadcast-stream-1#[0-1], yourSystem.broadcast-stream-2#2 +task.broadcast.inputs=yourSystem.global-stream-1#[0-1], yourSystem.global-stream-2#2 {% endhighlight %} If you use "[]", you are specifying a range. http://git-wip-us.apache.org/repos/asf/samza/blob/95ba041b/docs/learn/documentation/versioned/introduction/concepts.md ---------------------------------------------------------------------- diff --git a/docs/learn/documentation/versioned/introduction/concepts.md b/docs/learn/documentation/versioned/introduction/concepts.md index 25ef5ee..08b4557 100644 --- a/docs/learn/documentation/versioned/introduction/concepts.md +++ b/docs/learn/documentation/versioned/introduction/concepts.md @@ -59,7 +59,7 @@ The assignment of partitions to tasks never changes: if a task is on a machine t ### Dataflow Graphs -We can compose multiple jobs to create a dataflow graph, where the nodes are streams containing data, and the edges are jobs performing transformations. This composition is done purely through the streams the jobs take as input and output. The jobs are otherwise totally decoupled: they need not be implemented in the same code base, and adding, removing, or restarting a downstream job will not impact an upstream job. +We can compose multiple jobs to create a dataflow graph, where the edges are streams containing data, and the nodes are jobs performing transformations. This composition is done purely through the streams the jobs take as input and output. The jobs are otherwise totally decoupled: they need not be implemented in the same code base, and adding, removing, or restarting a downstream job will not impact an upstream job. These graphs are often acyclic—that is, data usually doesn't flow from a job, through other jobs, back to itself. However, it is possible to create cyclic graphs if you need to.
