You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Henry Cai (JIRA)" <ji...@apache.org> on 2016/05/03 00:22:12 UTC
[jira] [Commented] (KAFKA-3185) Allow users to cleanup internal
data
[ https://issues.apache.org/jira/browse/KAFKA-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267619#comment-15267619 ]
Henry Cai commented on KAFKA-3185:
----------------------------------
Second to this. It's very painful for us to test our demo program. We have to either change our application id or manually remove rocksDB or kafka log files.
> Allow users to cleanup internal data
> ------------------------------------
>
> Key: KAFKA-3185
> URL: https://issues.apache.org/jira/browse/KAFKA-3185
> Project: Kafka
> Issue Type: Sub-task
> Components: streams
> Reporter: Guozhang Wang
> 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)