[DRIVERS-564] Add support for majority read concern level to MapReduce Created: 23/Aug/18 Updated: 27/Oct/23 Resolved: 14/Feb/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||
| Description |
|
For The current plan is to emulate majority read concern level by waiting for w:majority in the portions of those operations that write (aggregations including $out and all map reduces) and keep the read concern level for the portions that don't (aggregations not including $out including all work from the shard phase). It is unclear right now which category inline map reduce falls under. Part of this work is to ensure that this approach is valid. |
| Comments |
| Comment by Jeremy Mikola [ 13/Mar/19 ] |
|
Note: Editing to remove mention of aggregate with $out, as that is handled by Also removing the SERVER fixVersion from this issue, as |
| Comment by Jeffrey Yemin [ 31/Aug/18 ] |
|
Aargh. Sorry, my bad. rathi.gnanasekaran not sure how to clear the Resolution field. |
| Comment by Bernie Hackett [ 31/Aug/18 ] |
|
jeff.yemin, this is about readConcern, not writeConcern. We do limit where we send readConcern. |
| Comment by Jeffrey Yemin [ 31/Aug/18 ] |
|
Drivers don't limit which write concern an application uses based on the operation. So there's nothing for drivers to do here. |