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

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

GitHub user mjsax opened a pull request:

    https://github.com/apache/kafka/pull/1671

    KAFKA-3185: [Streams] Added Kafka Streams Application Reset Tool

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mjsax/kafka resetTool-0.10.0.1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1671.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1671
    
----
commit 75e01c87a5de8a64b9d4b3baf2e0dd061e138b25
Author: Matthias J. Sax <matth...@confluent.io>
Date:   2016-06-11T12:12:42Z

    KAFKA-3185: [Streams] Added Kafka Streams Application Reset Tool
    
    cherry-picked from trunk
    
    Conflicts:
        checkstyle/import-control.xml
        streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java
        
streams/src/test/java/org/apache/kafka/streams/integration/utils/EmbeddedSingleNodeKafkaCluster.java

commit 1478653f08e3cfefe7f080572a41c38b3941775c
Author: Matthias J. Sax <matth...@confluent.io>
Date:   2016-07-27T22:28:28Z

    fixed cherry-pick issues

----


> Allow users to cleanup internal data
> ------------------------------------
>
>                 Key: KAFKA-3185
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3185
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>            Reporter: Guozhang Wang
>            Assignee: Matthias J. Sax
>            Priority: Blocker
>              Labels: user-experience
>             Fix For: 0.10.0.1
>
>
> Currently the internal data is managed completely by Kafka Streams framework 
> and users cannot clean them up actively. This results in a bad out-of-the-box 
> user experience especially for running demo programs since it results 
> internal data (changelog topics, RocksDB files, etc) that need to be cleaned 
> manually. It will be better to add a
> {code}
> KafkaStreams.cleanup()
> {code}
> function call to clean up these internal data programmatically.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to