[SERVER-11955] getLastError response for failed index build contains extra copy of "err" field Created: 04/Dec/13 Updated: 11/Jul/16 Resolved: 21/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Regression since 2.5.4. Repro with (mongo version 2.4, mongod version 57a4f169 (2.5.5-pre)):
Output:
|
| Comments |
| Comment by Randolph Tan [ 21/Jan/14 ] |
|
sridhar I believe the one you saw was a separate issue - |
| Comment by Sridhar Nanjundeswaran [ 17/Jan/14 ] |
|
The issues seems to have reappeared. With the 1/17 build );db.getLastErrorObj(); |
| Comment by Randolph Tan [ 13/Dec/13 ] |
|
getLastError will now wait for write concern regardless of whether an error occurred in the last operation (it doesn't on v2.4). And there is a chance that it will fail to do so, and will cause the command to return { ok: 0 }. |
| Comment by Githook User [ 13/Dec/13 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: |
| Comment by Scott Hernandez (Inactive) [ 05/Dec/13 ] |
|
Note that in |