You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@streams.apache.org by "Oliver Weiler (Jira)" <ji...@apache.org> on 2020/09/28 10:36:00 UTC
[jira] [Commented] (STREAMS-674) kafka-streams-application-reset
misses some internal topics
[ https://issues.apache.org/jira/browse/STREAMS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203143#comment-17203143 ]
Oliver Weiler commented on STREAMS-674:
---------------------------------------
BTW would love to contribute the patch!
> kafka-streams-application-reset misses some internal topics
> -----------------------------------------------------------
>
> Key: STREAMS-674
> URL: https://issues.apache.org/jira/browse/STREAMS-674
> Project: Streams
> Issue Type: Bug
> Affects Versions: 0.5.1
> Reporter: Oliver Weiler
> Priority: Major
>
> While the \{{kafka-streams-application-reset}} tool works in most cases, it misses some internal topics when using {{Foreign Key Table-Table Joins}}.
> After execution, there are still two internal topics left which were not deleted
> {code}
> bv4-indexer-KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000006-topic
> bbv4-indexer-717e6cc5-acb2-498d-9d08-4814aaa71c81-StreamThread-1-consumer bbv4-indexer-KTABLE-FK-JOIN-SUBSCRIPTION-RESPONSE-0000000014-topic
> {code}
> The reason seems to be the {{StreamsResetter.isInternalTopic}} which requires the internal topic to end with {{-changelog}} or {{-repartition}} (which the mentioned topics don't).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)