[ https://issues.apache.org/jira/browse/KAFKA-10721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231897#comment-17231897 ]
Matthias J. Sax commented on KAFKA-10721: ----------------------------------------- Interesting idea. I guess the current workaround would be as follows: {code:java} KStream streamA = builder.stream("topic"); KStream streamB = build.stream("other-topic").merge(streamA);{code} Overall, the workaround does not seem to be too bad. > Rewrite topology to allow for overlapping unequal topic subscriptions > --------------------------------------------------------------------- > > Key: KAFKA-10721 > URL: https://issues.apache.org/jira/browse/KAFKA-10721 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: A. Sophie Blee-Goldman > Priority: Minor > > Minor followup improvement to KAFKA-6687 in which we rewrite the topology to > make it possible for a user to subscribe multiple KStream/KTables to the same > topic or identical set of topics. We could further extend this to make it > possible for multiple KStream/KTables to be subscribed to overlapping but not > identical sets of topics, ie > {code:java} > KStream streamA = builder.stream("topic"); > KStream streamB = builder.stream("topic, "other-topic"); {code} > One way to do this would be to break up multiple-topic source nodes into > multiple single-topic sources that get merged together in the child node. > See > https://github.com/apache/kafka/pull/9582/files#diff-ac1bf2b23b80784dec20b00fdc42f2df7e5a5133d6c68978fa44aea11e950c3aR347-R349 -- This message was sent by Atlassian Jira (v8.3.4#803005)