[
https://issues.apache.org/jira/browse/KAFKA-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16701203#comment-16701203
]
Andy Bryant commented on KAFKA-7671:
------------------------------------
Hi [~mjsax],
I just checked the old versions (1.1, 1.0, 0.11, 0.10.2). Looks like the
{{repartitionRequired}} was set to {{false}} for globalKTable joins all the way
back to when the GlobalKTable was introduced in 0.10.2 with KAFKA-4490.
See
[https://github.com/apache/kafka/blob/0.10.2/streams/src/main/java/org/apache/kafka/streams/kstream/internals/KStreamImpl.java#L596]
Cheers
Andy
> 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
>
> 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)
