flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sihuazhou <...@git.apache.org>
Subject [GitHub] flink issue #6020: [FLINK-9373][state] Fix potential data losing for RocksDB...
Date Wed, 16 May 2018 13:42:47 GMT
Github user sihuazhou commented on the issue:

    https://github.com/apache/flink/pull/6020
  
    @StefanRRichter I had a look at the implementation of the iterators in RocksDB, I found
status just return the flag first `_status` as the result without any complex computation,
But for some `composite Iterator` like the `MergeIteraor` and `TwoLevelIterator` it need to
check all the `InternalIterator` they hold to decide the final status, and I also found the
iterator could be reset to `OK` in some cases...Hmm...do you think this is super cheap or
not?


---

Mime
View raw message