-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Layered Tables
-
Storage Engines - Foundations
-
651.322
-
None
-
None
On a disaggregated follower, a layered cursor value that is byte-identical to the internal tombstone (the two bytes 0x14 0x14) is reported as WT_NOTFOUND on read instead of returning the stored value.
Repro: on the follower, insert a key with value b'\x14\x14' (which lands in the ingest table), then search for that key. search() returns WT_NOTFOUND. A longer value sharing the same prefix (e.g. b'\x14\x14\xff') round-trips correctly.
- related to
-
WT-17933 Stop persisting encoded ingest tombstones prefixed values on disk
-
- Blocked
-
-
WT-18057 Layered tombstone decode guard triggered while persisting the recovery doc of an inflight chunk operation
-
- Investigating
-
-
WT-18130 Remove "non-tombstone trailing byte" assert in layered cursors
-
- Closed
-