Guozhang Wang commented on KAFKA-4327:

As we discussed before, it may not worth the effort since 1) most users are 
likely going to call the `streams reset` shell script in which they are likely 
going to having a core package installed anyways, 2) thinking about it twice, 
leaving the reset tool in `kafka.tools` is okay since it is where we put all 
the admin tooling classes; personally I think we could also consider 
`o.a.k.tools`, but again that is not very significant either.

> 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

Reply via email to