[KAFKA-7671] A KStream/GlobalKTable join shouldn't reset the repartition flag

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 1.1.2, 2.2.0, 2.1.1, 2.0.2
• Component/s: streams
• Assignee: Bill Bejeck
• Reporter: Andy Bryant
• Created: 26/Nov/18 00:24
• Updated: 29/Nov/18 02:32
• Resolved: 29/Nov/18 02:32

Description

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.

 

Issue Links

• links to: GitHub Pull Request #5959