[SERVER-66097] Investigate seek() behavior for column indexes Created: 29/Apr/22 Updated: 29/Oct/23 Resolved: 13/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm2646-m4 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
In regular b-tree indexes, there is some behavior in cursor seeking here that's necessary because WT::Cursor::search_near() is not guaranteed to return the maximum key that compares lower than the search key. We should determine whether we need equivalent logic for the column index. See here. |
| Comments |
| Comment by Githook User [ 13/Dec/22 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |