Github user sihuazhou commented on the issue: https://github.com/apache/flink/pull/5979 @StefanRRichter , the reason I prefer this approach is that: - From the comment in RocksDB's source we can find that deleteRange() should be used for deleting big range, what if the entries num of the map is not that big. - From the comments we can also find that deleteRange() would hurt the read performance, so we should consider to set ReadOptions::ignore_range_deletions = true to avoid the negative effect by deleteRange(), but if we use it for MapState.clear(), it seems that we can't set ReadOptions::ignore_range_deletions = true. And current approach should not bring any downside, what do you think?
---