[
https://issues.apache.org/jira/browse/KAFKA-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069222#comment-17069222
]
Maatari edited comment on KAFKA-6443 at 3/28/20, 5:18 AM:
----------------------------------------------------------
Hi all, is there a way to know what is the status of this ticket ? We are heavy
user of KTable multiple join including the scenario above, and have noticed
indeed, an unusual/substantial amount of intermediated result being generated
downstream
was (Author: maatdeamon):
Hi all, is there a way to know what is the status of this ticket ? We are heavy
user of KTable multiple join and have noticed indeed, an unusual/substantial
amount of intermediated result being generated downstream
> KTable involved in multiple joins could result in duplicate results
> -------------------------------------------------------------------
>
> Key: KAFKA-6443
> URL: https://issues.apache.org/jira/browse/KAFKA-6443
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Guozhang Wang
> Priority: Major
>
> Consider the following multi table-table joins:
> {code}
> table1.join(table2).join(table2); // "join" could be replaced with
> "leftJoin" and "outerJoin"
> {code}
> where {{table2}} is involved multiple times in this multi-way joins. In this
> case, when a new record from the source topic of {{table2}} is being
> processing, it will send to two children down in the topology and hence may
> resulting in duplicated join results depending on the join types.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
