[jira] [Commented] (KAFKA-3185) Allow users to cleanup internal data

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user mjsax opened a pull request:

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

    KAFKA-3185: Allow users to cleanup internal Kafka Streams data

    

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

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

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

    https://github.com/apache/kafka/pull/1636.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 #1636
    
----
commit d454d3d391c5838af0b232cd57e2f3b38ae70788
Author: Matthias J. Sax <ma...@confluent.io>
Date:   2016-06-11T12:12:42Z

    KAFKA-3185: [Streams] Added Kafka Streams cleanup client plus bash script

commit c397ad7fca6276ed1c45bb486999f59d5483b86d
Author: Matthias J. Sax <ma...@confluent.io>
Date:   2016-07-06T00:15:13Z

    minor fix: repartitioing

commit eeacd3a2f812395ead416412ccb7e5fe842543f1
Author: Matthias J. Sax <ma...@confluent.io>
Date:   2016-07-15T13:41:08Z

    moved local state store clean-up from script to library

----


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