[
https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154252#comment-16154252
]
Guozhang Wang commented on KAFKA-4327:
--------------------------------------
While reviewing KIP-171 I was thinking that we do not have to call
ConsumerGroupCommand to reset offsets, i.e. we just create a consumer and call
commit API or just use the CommitOffsetRequest directly (admittedly it will
have duplicated code). Thinking about it again I felt that this may not worth
the effort, so leaving it in Core is okay as it should be part of the admin
commands anyways.
> Move Reset Tool from core to streams
> ------------------------------------
>
> Key: KAFKA-4327
> URL: https://issues.apache.org/jira/browse/KAFKA-4327
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Jorge Quilcate
> Priority: Minor
>
> This is a follow up on https://issues.apache.org/jira/browse/KAFKA-4008
> Currently, Kafka Streams Application Reset Tool is part of {{core}} module
> due to ZK dependency. After KIP-4 got merged, this dependency can be dropped
> and the Reset Tool can be moved to {{streams}} module.
> This should also update {{InternalTopicManager#filterExistingTopics}} that
> revers to ResetTool in an exception message:
> {{"Use 'kafka.tools.StreamsResetter' tool"}}
> -> {{"Use '" + kafka.tools.StreamsResetter.getClass().getName() + "' tool"}}
> Doing this JIRA also requires to update the docs with regard to broker
> backward compatibility -- not all broker support "topic delete request" and
> thus, the reset tool will not be backward compatible to all broker versions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
