[SERVER-923] With upserts key can be in query or mod Created: 19/Jan/10 Updated: 12/Jul/16 Resolved: 14/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
These will work correctly: ) ) // converted to the first example. This must fail: ) This can cause dup IDs but wont fail until/unless we get unique indexes working across shards: |
| Comments |
| Comment by Mathias Stearn [ 14/May/10 ] |
|
Decided not to support 3rd case. Asserts if using a non-modifier update and key isn't in object. |
| Comment by Mathias Stearn [ 08/Feb/10 ] |
|
everything working but the 3rd case. deferring for now since it would behave differently under sharded and non-sharded environments |
| Comment by auto [ 19/Jan/10 ] |
|
Author: {'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}Message: better handling of sharded upserts. more update fixes coming after 1.3.1 |