[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:
Depends
depends on RUST-102 Add support for majority read concern... Closed
depends on SERVER-38117 Add support for majority read concern... Closed
depends on DRIVERS-2086 Add support for majority read concern... Closed
Related
is related to DRIVERS-610 Add support for majority read concern... Closed
is related to SERVER-20445 Add support for majority read concern... Closed
Driver Compliance:
Key Status/Resolution FixVersion
RUST-102 Duplicate

 Description   

For SERVER-20214 we are removing support for majority read concern level in these operations because we cannot write in that mode. This ticket is to reenable support.

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 DRIVERS-610. This ticket can remain in place for mapReduce support, since both depend on separate SERVER tickets.

Also removing the SERVER fixVersion from this issue, as SERVER-38117 is currently in the backlog.

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.

Generated at Thu Feb 08 08:21:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.