[SERVER-3642] make sure yieldSometimes RecordNeeds specs are appropriate Created: 18/Aug/11 Updated: 06/Dec/22 Resolved: 16/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
See QA-10 8) From a quick pass, in the following places it may make sense to change the in memory requirement spec: In some cases may only make sense to change after MaybeCovered mode has been implemented. |
| Comments |
| Comment by Chris Westin [ 06/Mar/12 ] |
|
We should improve this interface. It may not be known by the caller whether or not they can use WillNeed vs MaybeCovered, because the caller may not know what index is being used for the particular document that was just returned (or will be returned next). We have ways of using multiple indexes now, and the answer to this can vary as documents come out of the cursor. Therefore, this should be handled further down the call stack. At most, the caller knows what fields they require, but not whether or not they are available from the currently used index or not. |