[
https://issues.apache.org/jira/browse/KAFKA-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-7497:
-----------------------------------
Description: 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. (was: ref
[https://github.com/confluentinc/ksql/issues/2030]
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.)
> 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)
