[ https://issues.apache.org/jira/browse/KAFKA-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015405#comment-17015405 ]
Matthias J. Sax commented on KAFKA-9042: ---------------------------------------- Thanks for the PR [~high.lee] – note that this ticket requires a KIP (it's labled `needs-kip`). Hence, please first prepare a KIP and get it accepted before we can review and merge any PR. Details about the KIP process are described in the Kafka wiki: [https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals] > Auto infer external topic partitions in stream reset tool > --------------------------------------------------------- > > Key: KAFKA-9042 > URL: https://issues.apache.org/jira/browse/KAFKA-9042 > Project: Kafka > Issue Type: Improvement > Components: streams, tools > Reporter: Boyang Chen > Assignee: highluck > Priority: Major > Labels: needs-kip, newbie, newbie++ > > As of today, user has to specify `--input-topic` in the stream reset to be > able to reset offset to a specific position. For a stream job with multiple > external topics that needs to be purged, users usually don't want to name all > the topics in order to reset the offsets. It's really painful to look through > the entire topology to make sure we purge all the committed offsets. > We could add a config `--reset-all-external-topics` to the reset tool such > that when enabled, we could delete offsets for all involved topics. The topic > metadata could be acquired by issuing a `DescribeGroup` request from admin > client, which is stored in the member subscription information. -- This message was sent by Atlassian Jira (v8.3.4#803005)