[SERVER-20214] Stop supporting majority read concern level with MapReduce and Aggregation $out Created: 31/Aug/15 Updated: 24/Oct/17 Resolved: 17/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, MapReduce, Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Quint 9 09/18/15 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
We will not be supporting the majority read concern level on writing operations for 3.2. These operations write so they must error out if the user requests majority read concern level. |
| Comments |
| Comment by Githook User [ 17/Sep/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Andy Schwerin [ 09/Sep/15 ] |
|
Could you explain how w:majority ensure r:majority in sharded agg or mapreduce? I think that it does not since reads may come from nodes that take no writes. |
| Comment by Mathias Stearn [ 09/Sep/15 ] |
|
Changing ticket to reflect the decision not to support these operations with majority read concern. |