[SERVER-22414] Remove old writeConcern handling code from all commands Created: 01/Feb/16 Updated: 26/Apr/16 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 |
|
All commands that already support writeConcern in their own run() function, as opposed to in the centralized run() function, should have their writeConcern code removed. In this process, modify each command's supportsWriteConcern() function to return true. Also anywhere DBDirectClient is used, take this opportunity to replace it appropriately. |
| Comments |
| Comment by Judah Schvimer [ 12/Apr/16 ] |
|
Git commit: https://github.com/mongodb/mongo/commit/7ed530a55304bd9cc2b80c054f379b10d9cea8e2 |