[
https://issues.apache.org/jira/browse/KAFKA-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203616#comment-17203616
]
John Roesler commented on KAFKA-10530:
--------------------------------------
Thanks for the report [~oweiler] , and sorry for the trouble.
This report looks like https://issues.apache.org/jira/browse/KAFKA-9859, which
should have been _fixed_ in 2.6.0. Can you confirm that you still see this
issue in 2.6.0?
Thanks,
-John
> kafka-streams-application-reset misses some internal topics
> -----------------------------------------------------------
>
> Key: KAFKA-10530
> URL: https://issues.apache.org/jira/browse/KAFKA-10530
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.6.0
> 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)
