[SERVER-22604] Remove writeConcern from function signatures where it is unnecessary after writeConcern is more centralized Created: 12/Feb/16 Updated: 16/May/16 Resolved: 25/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.6 |
| Type: | Task | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 10 (02/19/16), Sharding 13 (04/22/16), Repl 14 (05/13/16) |
| Participants: |
| Description |
|
As part of making all commands that do writes accept write concern, many places that previously needed to take a writeConcern as an argument don't need to anymore. Go through and remove clean up those interfaces. |
| Comments |
| Comment by Githook User [ 25/Apr/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |