[
https://issues.apache.org/jira/browse/KAFKA-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16846795#comment-16846795
]
Bill Bejeck edited comment on KAFKA-7201 at 5/23/19 3:37 PM:
-------------------------------------------------------------
[~mjsax]
Apologies for the delayed response. Yes, this is resolved KAFKA-6761
was (Author: bbejeck):
[~mjsax]
Apologies for the delayed response. Yes this is resolved [link
KAFKA-6761|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)
