• A
    Fix range deletion handling in async MultiGet (#10534) · 65814a4a
    anand76 提交于
    Summary:
    The fix in https://github.com/facebook/rocksdb/issues/10513 was not complete w.r.t range deletion handling. It didn't handle the case where a file with a range tombstone covering a key also overlapped another key in the batch. In that case, ```mget_range``` would be non-empty. However, ```mget_range``` would only have the second key and, therefore, the first key would be skipped when iterating through the range tombstones in ```TableCache::MultiGet```.
    
    Test plan -
    1. Add a unit test
    2. Run stress tests
    
    Pull Request resolved: https://github.com/facebook/rocksdb/pull/10534
    
    Reviewed By: akankshamahajan15
    
    Differential Revision: D38773880
    
    Pulled By: anand1976
    
    fbshipit-source-id: dae491dbe52e18bbce5179b77b63f20771a66c00
    65814a4a
db_basic_test.cc 151.2 KB