[SERVER-1060] multi-update only affects Created: 28/Apr/10 Updated: 12/Jul/16 Resolved: 28/Apr/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | 1.4.0, 1.4.1, 1.4.2, 1.5.0 |
| Fix Version/s: | 1.4.3, 1.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Cowgill | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MacOSX 64-bit, Ubuntu Karmic |
||
| Participants: |
| Description |
|
Multi update doesn't affect all matching documents. As far as I can tell, the bug only occurs when the query is able to use an index. This mongo shell transcript demonstrates the problem: > db.foo.drop(); ) ); } > db.foo.update( {k: 'x'}, {$push: {a: 'y'}}, false, true); > If I omit the ensureIndex call, all of the documents are updated correctly. Tested in 1.2.2, 1.4.0, 1.4.2, and the most recent nightly dev build (v1.5.1-pre). |
| Comments |
| Comment by auto [ 03/May/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: more aggressive about checking for index moves in multi-update |
| Comment by auto [ 28/Apr/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: more aggressive about checking for index moves in multi-update |