You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Dmitry Minkovsky (JIRA)" <ji...@apache.org> on 2016/06/17 19:53:05 UTC

[jira] [Commented] (KAFKA-3862) Kafka streams documentation: partition<->thread<->task assignment unclear

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

Dmitry Minkovsky commented on KAFKA-3862:
-----------------------------------------

Oh hey, I somehow missed 0.10 and Confluent 3.0. Current version of docs are much clearer/don't have this issue. 

> Kafka streams documentation: partition<->thread<->task assignment unclear
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-3862
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3862
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.0.0
>         Environment: N/A
>            Reporter: Dmitry Minkovsky
>            Assignee: Guozhang Wang
>            Priority: Minor
>             Fix For: 0.10.0.0
>
>
> Hi. Not sure if this is the right place to post about documentation (this isn't actually a software bug).
> I believe the following span of documentation is self-contradictory:
> !http://i.imgur.com/WM8ada2.png!
> In the paragraph text before and after the image, it says the partitions are *evenly distributed* among the threads. However, in the image, Thread 1 gets p1 and p3 (4 partitions, total) while Thread 2 gets p2 (2 partitions, total). That's "even" in the sense that you can't do any better, but still not even, and in conflict with the text that follows the image:
> !http://i.imgur.com/xq3SOre.png!
> This doesn't make sense because why would p2 from topicA and topicB go to different threads? if this were the cause, you couldn't join the partitions, right?
> Either way, it seems like the two things are in conflict.
> Finally, the wording:
> bq. ...assume that each thread executes a single stream task...
> What does "assume" mean here? I've not seen any indication elsewhere in the documentation that shows you can configure this behavior. Sorry if I missed this.
> Thank you!



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