You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Bill Bejeck (JIRA)" <ji...@apache.org> on 2019/05/23 15:39:00 UTC
[jira] [Resolved] (KAFKA-7201) Optimize repartition operations
[ https://issues.apache.org/jira/browse/KAFKA-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Bejeck resolved KAFKA-7201.
--------------------------------
Resolution: Fixed
Resolved via https://issues.apache.org/jira/browse/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
>
> 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)