diff options
author | Keith Bostic <keith@wiredtiger.com> | 2014-09-11 10:05:45 -0400 |
---|---|---|
committer | Keith Bostic <keith@wiredtiger.com> | 2014-09-11 10:05:45 -0400 |
commit | 60751aaba624cf364acc1a45f4007f2b031135d3 (patch) | |
tree | b8dfa4253906c9fc8ada45d16e0f36ebae8d52ae | |
parent | 4a901b42ab03a708de27c31a0bc6c9ad582191aa (diff) | |
download | mongo-60751aaba624cf364acc1a45f4007f2b031135d3.tar.gz |
LSM tombstones are no longer empty values, remove that caveat from
the LSM page.
-rw-r--r-- | src/docs/lsm.dox | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/docs/lsm.dox b/src/docs/lsm.dox index 0313862afdf..d5439d6209e 100644 --- a/src/docs/lsm.dox +++ b/src/docs/lsm.dox @@ -107,12 +107,6 @@ there are chunks in the tree for each cursor that is open on the LSM tree. The number of hazard pointers is configured with the \c "hazard_max" configuration key to ::wiredtiger_open. -@subsection lsm_tombstones Empty values - -Internally, WiredTiger's LSM trees use an empty value to represent a -record that has been removed (also known as a "tombstone"). For this -reason, applications cannot store records in LSM trees with empty values. - @subsection lsm_checkpoints Named checkpoints Named checkpoints are not supported on LSM trees, and cursors cannot be opened |