[SERVER-13015] 2.6.0-rc0: Update that violates sparse index is not done, generates no complaint. Created: 03/Mar/14 Updated: 07/Mar/14 Resolved: 04/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Cross | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When updating a value to another value that it cannot take because of a unique index, the update fails, but no error is generated. This is bad b/c the update method found the document, and would have performed the update without the index, but does not complain. Users may think the update worked awesomely, but be wrong. Steps to Reproduce:
|
| Comments |
| Comment by William Cross [ 04/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
Verified. Thanks for the help with this! | ||||||||||||||||||||||||||||||||||
| Comment by William Cross [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
Other possible weird stuff: I have some other mongod's running on this box.
| ||||||||||||||||||||||||||||||||||
| Comment by William Cross [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
I have two v2.6 mongo shells open in different tabs in iTerm 2. | ||||||||||||||||||||||||||||||||||
| Comment by William Cross [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
You can grep for version() above. | ||||||||||||||||||||||||||||||||||
| Comment by William Cross [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
My full shell output:
| ||||||||||||||||||||||||||||||||||
| Comment by William Cross [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
Sending more info from the shell. We're dealing with the possibility that I've got a weird shell situation, and are debugging that. | ||||||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 03/Mar/14 ] | ||||||||||||||||||||||||||||||||||
|
You do not appear to be using the 2.6 shell (note that you do not have a WriteResult), nor calling getLastError() immediately after the write so something is suspect in your example/environment. I cannot reproduce this. Here is my output:
We can re-open if you can provide more detail about your environment and reproduction case. |