[ https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701416#comment-16701416 ]
Matthias J. Sax commented on KAFKA-7671: ---------------------------------------- I marked fixed version as 2.2.0 and 2.1.1 for now, to make sure we fix it for those release. We should try to back port the fix to older versions, too, though. > A KStream/GlobalKTable join shouldn't reset the repartition flag > ---------------------------------------------------------------- > > Key: KAFKA-7671 > URL: https://issues.apache.org/jira/browse/KAFKA-7671 > Project: Kafka > Issue Type: Improvement > Components: streams > Affects Versions: 2.0.1 > Reporter: Andy Bryant > Priority: Major > Fix For: 2.2.0, 2.1.1 > > > Currently a KStream/GlobalKTable join resets the repartition required flag to > false. > I have a topology where I map a stream, join with a GlobalKTable, then > groupByKey then aggregate. > The aggregate wasn't behaving correctly because it didn't force a repartition > as I expected. The KStream/GlobalKTable join had reset the flag and hence I > was getting the same keys in different partitions. > Since a KStream/GlobalKTable join does not itself force a repartition, it > should simply propagate the flag down to the resultant KStream the same way > most other operators work. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)