-
Type:
Build Failure
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Layered Tables
-
None
-
Storage Engines, Storage Engines - Foundations, Storage Engines - Transactions
-
None
-
3
Currently, __clayered_iterate checks whether the entry has been deleted on the current_cursor, which may point to either the ingest table or the stable table. Since only the ingest table can return tombstoned values, this logic could be restricted to the ingest table. That would simplify the code structure and avoid unnecessary checks.
- is related to
-
WT-17014 Fix out of order in layered cursor because of prepare conflict
-
- Closed
-