mirror of
https://github.com/facebook/rocksdb.git
synced 2026-07-07 14:47:40 +08:00
Include PR and version for range tombstone blog post (#14875)
Summary: Pull Request resolved: https://github.com/facebook/rocksdb/pull/14875 title Reviewed By: pdillinger Differential Revision: D109353179 fbshipit-source-id: c14c9ecbd29a8118b1d0f0689e2f29c162bd15e8
This commit is contained in:
committed by
meta-codesync[bot]
parent
30f42e00ba
commit
f8987bc7b9
@@ -65,7 +65,7 @@ Because the tombstone lives in the memtable, it follows the normal lifecycle fro
|
||||
|
||||
## Enabling it
|
||||
|
||||
Range tombstone conversion is controlled by the column-family option `min_tombstones_for_range_conversion`: the minimum length of a contiguous point-tombstone run that triggers a conversion. The default is `0`, which disables the feature. Set it to a positive value to turn it on; the option is dynamically changeable through `SetOptions`, so you can enable or tune it without reopening the database.
|
||||
Range tombstone conversion landed in [PR #14448](https://github.com/facebook/rocksdb/pull/14448) (plus a few additional follow-up bug fixes) and is available in RocksDB 11.3.0 and later. It is controlled by the column-family option `min_tombstones_for_range_conversion`: the minimum length of a contiguous point-tombstone run that triggers a conversion. The default is `0`, which disables the feature. Set it to a positive value to turn it on; the option is dynamically changeable through `SetOptions`, so you can enable or tune it without reopening the database.
|
||||
|
||||
```cpp
|
||||
Options options;
|
||||
|
||||
Reference in New Issue
Block a user