The comparison between the cursor's current key and the search key should follow the same semantics as the previous search_near call, whereby a search key that is fully a prefix of a larger cursor key should return that we've landed past the search key (or after the search key for a backward cursor).
Failing to do so can fail this assertion on debug builds. This happens when search_near lands - by design - on a key that is lower than the search key (or after the search key on backward cursors).
- is duplicated by
-
SERVER-66917 InsertAndSeekKeyString unit test should use makeKeyStringForSeek
- Closed
- is related to
-
WT-9323 Fix a race tracking whether a tree has updates after a checkpoint
- Closed