[SERVER-17458] Update with upsert true with _id 'in' x query does not work in hashed sharded collection Created: 04/Mar/15 Updated: 10/Mar/15 Resolved: 10/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.6.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Breitlauch | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | 1. Take a sharded collection with shard key: { _id : "hashed"}.
|
||||||||
| Participants: | |||||||||
| Description |
|
We have a sharded collection with shard key: { _id : "hashed"}.
This only happens on sharded collections + upsert: true + _id: { $in: [ 2, 3 ] } query. if the query is not an in query or upsert is false it works. |
| Comments |
| Comment by Andy Schwerin [ 10/Mar/15 ] |
|
This is essentially a duplicate of |
| Comment by Andy Schwerin [ 06/Mar/15 ] |
|
ramon.fernandez, can you try the reporter's repro on the 3.0 branch? The targeting code with respect to upserts changed during the development of 3.0? This problem may have been resolved by the work done for |