Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
Query 2018-07-16, Query 2018-07-30, Query 2018-10-22, Query 2018-11-05, Query 2018-11-19
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.
Attachments
Issue Links
- is depended on by
-
DRIVERS-610 Add support for majority read concern level to Aggregation $out
-
- Closed
-
-
PHPLIB-290 Remove aggregate() and restriction on majority read concern
-
- Closed
-
- is documented by
-
DOCS-12598 Docs for SERVER-20445: Add support for majority read concern level to Aggregation $out
-
- Closed
-
- related to
-
DRIVERS-564 Add support for majority read concern level to MapReduce
-
- Closed
-
-
SERVER-36925 All write operations with a query component should support readConcern
-
- Closed
-
-
SERVER-38117 Add support for majority read concern level to MapReduce
-
- Closed
-
-
SERVER-20214 Stop supporting majority read concern level with MapReduce and Aggregation $out
-
- Closed
-
-
SERVER-36255 Prohibit $out with readConcern level "linearizable"
-
- Closed
-
-
DOCS-10647 Document readConcern option for inline mapReduce
-
- Closed
-