[SERVER-22421] Add writeConcernError backwards compatibility to User Management Commands Created: 01/Feb/16 Updated: 24/Apr/18 Resolved: 12/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | 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 | ||||||||
| Sprint: | Sharding 10 (02/19/16), Sharding 11 (03/11/16), Sharding 12 (04/01/16), Sharding 13 (04/22/16) | ||||||||
| Participants: | |||||||||
| Description |
|
When they receive a writeConcernError, write commands should return a response with the format:
User Managements Commands currently have a response format of {"ok" : 0, "errmsg" : "timeout", "code" : 8 }. These commands need to return the new format in addition to or instead of the old format. To do so, inside of Command::run(), when we get a writeConcernError we will simply check if the command is a UserManagementCommand and if so we will set ok to 0, and add "errmsg" and "code" fields with the errmsg and code from the writeConcernError. |
| Comments |
| Comment by Judah Schvimer [ 17/Jan/18 ] | ||
|
| ||
| Comment by Gabriel Russell (Inactive) [ 17/Jan/18 ] | ||
|
judah.schvimer, I just saw this comment in master:
I just wanted to alert you in case you wanted to get that code removed. | ||
| Comment by Githook User [ 12/Apr/16 ] | ||
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |