[ 
https://issues.apache.org/jira/browse/KAFKA-9042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014461#comment-17014461
 ] 

ASF GitHub Bot commented on KAFKA-9042:
---------------------------------------

highluck commented on pull request #7948: KAFKA-9042: Auto infer external topic 
partitions in stream reset tool
URL: https://github.com/apache/kafka/pull/7948
 
 
   https://issues.apache.org/jira/browse/KAFKA-9042
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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)

Reply via email to