[
https://issues.apache.org/jira/browse/KAFKA-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Levani Kokhreidze resolved KAFKA-9859.
--------------------------------------
Fix Version/s: 2.6.0
Resolution: Fixed
fixed with PR [https://github.com/apache/kafka/pull/8671]
> 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
> Assignee: Levani Kokhreidze
> Priority: Major
> Labels: newbie, newbie++
> Fix For: 2.6.0
>
>
> Steps to reproduce:
> * Create Kafka Streams application which uses foreign key join operation
> (without a Named parameter overload)
> * 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|#L679-L680]] uses
> `-subscription-registration-topic` and `-subscription-response-topic`
> suffixes to match topics generated by the foreign key operation. While in
> reality, internal topics are generated in this format:
> {code:java}
> <application id>-KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-<running
> number>-topic
> <application id>-KTABLE-FK-JOIN-SUBSCRIPTION-RESPONSE-<running
> number>-topic{code}
> Please note that this problem only happens when `Named` parameter is not
> used. When named parameter is used, topics are generated with a same pattern
> as specified in StreamsResetter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
