Myasuka opened a new pull request #12736:
URL: https://github.com/apache/flink/pull/12736


   ## What is the purpose of the change
   This PR is based on previous PR of 
https://github.com/apache/flink/pull/12514 and fixed the error at FLINK-18338.
   
   Flink open RocksDB column family options configuration for users. However, 
user might misuse `OptimizeForPointLookup` which lead to RocksDB timer and map 
state did not give correct result.
   
   The perfect solution is to bump RocksDB version larger than 6.2.2 (see 
https://github.com/facebook/rocksdb/issues/6893 ), however, this might be 
better done in release-1.12 cycle and we use explicitly `new 
ReadOptions().setTotalOrderSeek(true)` to pass to RocksDB iterators to ensure 
the seek order.
   
   ## Brief change log
   
     - Add method `RocksDBOperationUtils#createTotalOrderSeekReadOptions` to 
create read options and pass this to places where need a RocksDB iterator.
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - Added test `RocksDBStateMisuseOptionTest` to cover `MapState` and 
`Timer` case when misusing `optimizeForPointLookup`.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): **should no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to