[
https://issues.apache.org/jira/browse/KAFKA-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091216#comment-17091216
]
Kin Siu commented on KAFKA-9859:
--------------------------------
I have been using 2.4.1 to perform application reset, but there are topics of
foreignKey join operation left in broker after reset.
Looks to me the suffix added for foreignKey, and the actual one generated is
different.
e.g. topics left behind after reset has suffix of "-topic" :
```
<application id>-KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-<running
number>-topic
<application id>-KTABLE-FK-JOIN-SUBSCRIPTION-RESPONSE-<running number>-topic
```
Should I raise a new JIRA?
> 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)
