[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:
Depends
depends on DRIVERS-254 Add support for the readConcern option. Closed
Related
related to DOCS-10647 Document readConcern option for inlin... Closed
related to PHPLIB-290 Remove aggregate() and restriction on... Closed
is related to SERVER-20445 Add support for majority read concern... Closed
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: SERVER-20214 Stop supporting majority read concern level with MapReduce and Aggregation $out
Branch: master
https://github.com/mongodb/mongo/commit/79e06f2353b6bdd0748ab1ee83c03ca7b33683f7

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.

Generated at Thu Feb 08 03:53:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.