[ 
https://issues.apache.org/jira/browse/SAMZA-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038844#comment-15038844
 ] 

Yi Pan (Data Infrastructure) commented on SAMZA-828:
----------------------------------------------------

Simply adding the patch here, since it is simple doc change:
{noformat}
diff --git a/docs/learn/documentation/versioned/jobs/configuration-table.html 
b/docs/learn/documentation/versioned/jobs/configuration-table.html
index 2e09cd1..6705530 100644
--- a/docs/learn/documentation/versioned/jobs/configuration-table.html
+++ b/docs/learn/documentation/versioned/jobs/configuration-table.html
@@ -482,7 +482,7 @@
                        or <span class="system">system-name</span>.<span 
class="stream">stream-name</span>#[<i>startingPartitionId</i>-<i>endingPartitionId</i>]</dt>
                        </dl>
                        <dl>
-                            <dt>Example: 
<code>task.broadcast.inputs=mySystem.broadcastStream#[1-2], 
mySystem.broadcastStream#1</code></dt>
+                            <dt>Example: 
<code>task.broadcast.inputs=mySystem.broadcastStream#[0-2], 
mySystem.broadcastStream#0</code></dt>
                        </dl>
                     </td>
                 </tr>
{noformat}

> Config task.broadcast.inputs documentation is confusing
> -------------------------------------------------------
>
>                 Key: SAMZA-828
>                 URL: https://issues.apache.org/jira/browse/SAMZA-828
>             Project: Samza
>          Issue Type: Improvement
>          Components: docs
>    Affects Versions: 0.10.0
>            Reporter: Rick Mangi
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> The example for configuring a stream by partition uses:
> Example: task.broadcast.inputs=mySystem.broadcastStream#[1-2], 
> mySystem.broadcastStream#1
> Kafka partitions start with index 0. It's very confusing to have both 
> examples start at index 1. This threw me for a bit before I realized that the 
> example was misleading. Not handling partition 0 caused my tasks to crash at 
> startup.



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

Reply via email to