[
https://issues.apache.org/jira/browse/KAFKA-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722005#comment-17722005
]
Matthias J. Sax commented on KAFKA-13349:
-----------------------------------------
Yes, we want to add `remove()` to interface
[https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/state/KeyValueIterator.java]
and thus all implementation will need to support it.
> Allow Iterator.remove on KeyValueIterator
> -----------------------------------------
>
> Key: KAFKA-13349
> URL: https://issues.apache.org/jira/browse/KAFKA-13349
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Guozhang Wang
> Priority: Major
> Labels: needs-kip, newbie++
>
> Today Stream's state store's range iterator does not support `remove`. We
> could consider adding such support for all the built-in state stores:
> * RocksDB's native iterator does not support removal, but we can always do a
> delete(key) concurrently while the iterator is open on the snapshot.
> * In-Memory: straight forward implementation.
> The benefit of that is then for range-and-delete truncation operation we do
> not necessarily have to be cautious about concurrent modification exceptions.
> This could also help GC with in-memory stores.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
