[SERVER-1053] UpdateOp just looks for first match, even with multi updates Created: 26/Apr/10  Updated: 12/Jul/16  Resolved: 16/Jan/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

we could potentially choose the index based on more than the first match if we're doing a multi update (for example see how DeleteOp works)



 Comments   
Comment by Eliot Horowitz (Inactive) [ 16/Jan/14 ]

new query optimizer does something like this

Generated at Thu Feb 08 02:55:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.