[SERVER-42983] Improve Biggie's seekAfterProcessing implementation Created: 22/Aug/19 Updated: 17/Jul/20 Resolved: 17/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Henrik Edin |
| Resolution: | Done | Votes: | 0 |
| Labels: | intern_ephemeral_for_test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Execution Team 2020-06-29, Execution Team 2020-07-13, Execution Team 2020-07-27 |
| Participants: |
| Description |
|
Currently, seekAfterProcessing has confusing branching based on combinations of _forward and inclusive. The keyStringVal parameter should have those information encoded, so seekAfterProcessing should directly use keyStringVal to do the comparison just like WiredTigerIndex. |
| Comments |
| Comment by Henrik Edin [ 17/Jul/20 ] |
|
|