[SERVER-77189] Ensure UpdateNoIndexes is propagated correctly Created: 16/May/23 Updated: 31/May/23 Resolved: 31/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Colin Stolley | Assignee: | Colin Stolley |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backport Requested: |
v7.0
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 105 | ||||||||
| Description |
|
When calling updateDocument() here: Note that we compute the diff from the OpLog event, but there are only 2 choices: either the diff from the the oplog, or all indexes have been changed. But there is a third option: No indexes have changed. We need to pass that value through and handle it correctly in updateRecord() to avoid updating more indexes than we should, and to avoid going through the anyIndexesMightBeAffected() checks if it isn't needed. |
| Comments |
| Comment by Colin Stolley [ 31/May/23 ] |
|
This has been obviated by |