[ https://issues.apache.org/jira/browse/KAFKA-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648105#comment-16648105 ]
Guozhang Wang commented on KAFKA-7497: -------------------------------------- [~mjsax] You're right, I was only thinking about the use cases that the stream needs some enrichment that are independent of any other streams / tables; I also agree with you that even with sliding window, it seems windowed aggregations should be sufficient still. [~rmoff] I looked at the use case, and it seems to be a better fit with "session window" aggregations of KStream than using KStream self-join: https://kafka.apache.org/20/javadoc/org/apache/kafka/streams/kstream/SessionWindows.html > Kafka Streams should support self-join on streams > ------------------------------------------------- > > Key: KAFKA-7497 > URL: https://issues.apache.org/jira/browse/KAFKA-7497 > Project: Kafka > Issue Type: New Feature > Components: streams > Reporter: Robin Moffatt > Priority: Major > Labels: needs-kip > > There are valid reasons to want to join a stream to itself, but Kafka Streams > does not currently support this ({{Invalid topology: Topic foo has already > been registered by another source.}}). To perform the join requires creating > a second stream as a clone of the first, and then doing a join between the > two. This is a clunky workaround and results in unnecessary duplication of > data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)