[ https://issues.apache.org/jira/browse/KAFKA-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012736#comment-16012736 ]
Tommy Becker commented on KAFKA-5256: ------------------------------------- Well ideally it is idempotent yes, but consider the scenario where the streams application is down for longer than the tombstone retention period. In that time a deletion can happen, both the original message and the tombstone are compacted away, but the data is still in the store. > Non-checkpointed state stores should be deleted before restore > -------------------------------------------------------------- > > Key: KAFKA-5256 > URL: https://issues.apache.org/jira/browse/KAFKA-5256 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 0.10.2.1 > Reporter: Tommy Becker > > Currently, Kafka Streams will re-use an existing state store even if there is > no checkpoint for it. This seems both inefficient (because duplicate inserts > can be made on restore) and incorrect (records which have been deleted from > the backing topic may still exist in the store). Since the contents of a > store with no checkpoint are unknown, the best way to proceed would be to > delete the store and recreate before restoring. -- This message was sent by Atlassian JIRA (v6.3.15#6346)