[SERVER-2405] mongos does not report unique index insert failure on non-sharded collection Created: 25/Jan/11 Updated: 12/Jul/16 Resolved: 25/Jan/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 1.6.4 |
| Fix Version/s: | 1.7.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Brown | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
javascript shell or ruby driver connected to mongos running on linux to sharded replicata set mongod(s) running on linux |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
When trying to write duplicate data to a collection that is not sharded and has a unique index, the data will not be written, but no error is reported to the driver / console. If the same query is ran connected directly to mongod (instead of through mongos) the error is reported. |