-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Component/s: Layered Tables
-
Storage Engines - Foundations
-
1,082.499
-
SE Foundations - 2026-08-04, SE Foundations - 2026-08-18
-
8
Currently, the layered cursors implementation applies encoding logic for ingest tombstone-prefixed values (everything starting with \x14\x14) to both ingest and stable tables. This encoding logic is only required for ingest tables, but as a result, affected entries may be persisted on disk via the stable table, even though this is unnecessary.
This is a problem because once data is persisted on disk, it becomes a data format compatibility guarantee and therefore cannot be removed. However, this logic is only needed for the current ingest tombstone design, and if we change that design in the future, it would no longer be required at all.
Because of this, we should assess whether any customers have entries affected by this behavior and try to find a way to remove it as soon as possible.
- is related to
-
-
- Closed
-
-
WT-18244 Route layered cursor value transfers through encode/decode wrappers - WT-18194 followup
-
- Open
-
-
-
- Backlog
-
- related to
-
-
- Open
-
-
-
- Open
-
-
-
- Open
-
-
WT-18130 Remove "non-tombstone trailing byte" assert in layered cursors
-
- Closed
-