-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Execution Team 2022-08-08, Execution Team 2022-08-22, Execution Team 2022-10-03, Storage Engines - 2022-10-31
Unique index duplicate key check searches for the key's existence before insertion into the index. search_near cursor API is used for the purpose. With durable history, the search through a table with a lot of deleted content became more expensive hence causing regression with insertion into the unique indexes. A prefix-search API was added that would cause search_near to early exit if the search was past the prefix. The prefix-search is being replaced by a feature to configure bounds on a cursor.
An existing prefix search can be replaced with a cursor bound on the prefix. This ticket will do so for the above-mentioned unique index usage in the server.
- depends on
-
WT-9324 Add additional logic to cursor->search_near to handle range bounds.
- Closed
- related to
-
SERVER-61185 Use prefix_search for unique index lookup
- Closed
-
SERVER-68380 Always use bounded WT cursors instead of search_near
- Closed