You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "John Roesler (Jira)" <ji...@apache.org> on 2020/10/05 18:06:00 UTC
[jira] [Resolved] (KAFKA-10530) kafka-streams-application-reset
misses some internal topics
[ https://issues.apache.org/jira/browse/KAFKA-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Roesler resolved KAFKA-10530.
----------------------------------
Resolution: Duplicate
Closing now, since this seems like a duplicate report, and visual code inspection indicates it should have been fixed.
If you do still see this [~oweiler] , please feel free to re-open the ticket.
> 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, tools
> 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)