-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
Fully Compatible
-
Execution Team 2023-12-25, Execution Team 2024-01-08, Execution Team 2024-01-22
-
20
The new WT_CURSOR bound feature is more efficient than a search_near if we set a lower bound and call next() or set an upper bound and call prev().
The important cases we know about are already tracked in other tickets, but there is at least one case in seekNear that could take advantage of a bounded cursor.
- depends on
-
WT-11911 Fix use-after-free with bounded cursor and search_near
- Closed
-
WT-11957 Calling next() is not idempotent with bounded cursors and prepare conflicts
- Closed
- is related to
-
SERVER-84748 Index cursors no longer need callers to provide KeyStrings with discriminators
- Backlog
-
SERVER-65527 Use range bounded cursors in place of prefix search_near on unique indexes
- Closed
-
SERVER-69093 Use range bounded cursors for restoring cursors in the record store after yielding
- Closed
- related to
-
SERVER-78365 Investigate removing ignore_prepare=force
- In Progress