You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/10/02 18:36:00 UTC

[jira] [Comment Edited] (KAFKA-7201) Optimize repartition operations

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

Matthias J. Sax edited comment on KAFKA-7201 at 10/2/18 6:35 PM:
-----------------------------------------------------------------

Seems to be contained (and thus resolved) via KAFKA-6761?


was (Author: mjsax):
Seems to be contained (and thus resolved via KAFKA-6761)?

> Optimize repartition operations
> -------------------------------
>
>                 Key: KAFKA-7201
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7201
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Bill Bejeck
>            Assignee: Bill Bejeck
>            Priority: Major
>             Fix For: 2.2.0
>
>
> When the topology has a key changing operation, any downstream processors using the key will automatically create a repartition topic.  In most cases these multiple repartition topics can be collapsed into one repartition operation occurring immediately after the key changing operation, thus reducing streams overall footprint.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)