[
https://issues.apache.org/jira/browse/KAFKA-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091227#comment-17091227
]
Tom Mau commented on KAFKA-9859:
--------------------------------
Looks like the topic pattern it looking for in
`kafka.tools.StreamsResetter#isInternalTopic` does not match the generated
internal topic name
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/tools/StreamsResetter.java#L679-L680]
{code:java}
topicName.endsWith("-subscription-registration-topic")
topicName.endsWith("-subscription-response-topic"){code}
> kafka-streams-application-reset tool doesn't take into account topics
> generated by KTable foreign key join operation
> --------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-9859
> URL: https://issues.apache.org/jira/browse/KAFKA-9859
> Project: Kafka
> Issue Type: Bug
> Components: streams, tools
> Reporter: Levani Kokhreidze
> Priority: Major
>
> Steps to reproduce:
> * Create Kafka Streams application which uses foreign key join operation
> * Stop Kafka streams application
> * Perform `kafka-topics-list` and verify that foreign key operation internal
> topics are generated
> * Use `kafka-streams-application-reset` to perform the cleanup of your kafka
> streams application: `kafka-streams-application-reset --application-id
> <your_app_id> --input-topics <your_input_topic> --bootstrap-servers
> <your_bootstrap_server> --to-datetime 2019-04-13T00:00:00.000`
> * Perform `kafka-topics-list` again, you'll see that topics generated by the
> foreign key operation are still there.
> `kafka-streams-application-reset` uses `repartition` and `changelog` suffixes
> to determine which topics needs to be deleted, as a result topics generated
> by the foreign key are ignored.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
