[SERVER-38117] Add support for majority read concern level to MapReduce Created: 13/Nov/18  Updated: 27/Oct/23  Resolved: 04/Feb/22

Status: Closed
Project: Core Server
Component/s: MapReduce
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Martin Neupauer Assignee: Backlog - Query Optimization
Resolution: Gone away Votes: 0
Labels: query-44-grooming
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-564 Add support for majority read concern... Closed
is depended on by DRIVERS-2086 Add support for majority read concern... Closed
Related
related to PHPLIB-290 Remove aggregate() and restriction on... Closed
is related to SERVER-20445 Add support for majority read concern... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

The original ticket SERVER-20445 added majority read concern to $out only. This is the follow up for MapReduce.



 Comments   
Comment by Esha Bhargava [ 04/Feb/22 ]

Closing these tickets as part of the deprecation of mapReduce.

Comment by Charlie Swanson [ 09/Jul/19 ]

pawel.terlecki we're not planning on doing this as part of PM-766. See this non-goal in the scope:

Removing any restrictions of usage of mapReduce. We do not plan to make the command available within transactions (which will require PM-1247), nor do we plan on removing any restrictions on readConcern, writeConcern, or similar options.

I don't think it will be technically challenging to do this once we complete PM-766, but we were trying to keep the scope as limited as possible so chose not to investigate here.

Comment by Pawel Terlecki [ 09/Jul/19 ]

charlie.swanson, james.wahlin would this be easier after MR in Agg completes? Is it worth including this in that epic?

Generated at Thu Feb 08 04:48:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.