[SERVER-3657] Don't treat updates without upsert as a save() in sharding Created: 19/Aug/11 Updated: 11/Jul/16 Resolved: 30/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We currently do the wrong thing on updates like db.foo.update({_id:1}, {$inc:{a:1}}). We need to treat it as multi unless sharding by _id. |
| Comments |
| Comment by Vinaykr [ 29/Apr/12 ] |
|
I second that. Would be great if this can be backported to 2.0 . |
| Comment by Geoffrey Gallaway [ 29/Apr/12 ] |
|
Could this be backported to the 2.0 series? |
| Comment by auto [ 06/Feb/12 ] |
|
Author: {u'login': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Refactor sharded update routing and validation code |