-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Component/s: None
-
None
The Read Concern specification details the specifics of implementing read concern in your driver. You'll find that it is very similar to write concern.
How it looks like for commands:
db.runCommand({
find: ....,
readConcern : {
level: “[majority|local]”
}
});
Note: readConcern is only supported for the new find command helper, not legacy OP_QUERY queries.
New URI option:
mongodb://server:27017/db?readConcernLevel=[majority|local]
The commands that accept read concern are listed below:
- find
- aggregate without $out
- mapReduce when the result is inline
- distinct
- count
- parallelCollectionScan
- geoNear
- geoSearch
You only need to add support for these commands to your helper methods. Users using the runCommand method on your database object will need to supply a readConcern manually.
- depends on
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is depended on by
-
SERVER-20214 Stop supporting majority read concern level with MapReduce and Aggregation $out
-
- Closed
-
- related to
-
SERVER-18022 Support "read committed" isolation level where "committed" means confirmed by the voting majority of a replica set
-
- Closed
-