-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Replication
-
ALL
-
v5.0
-
Repl 2021-06-28
When we try to open a change stream on the server configured with the ephemeralForTest (biggie in 4.4) storage engine, the server should provide an informative error message similar to the behavior in 4.4:
"operationTime" : Timestamp(0, 0), "ok" : 0, "errmsg" : "Storage engine does not support read concern: { readConcern: { level: \"majority\" } }", "code" : 148, "codeName" : "ReadConcernMajorityNotEnabled",
Affects master and 5.0 only.
- is related to
-
SERVER-39356 Change stream updateLookup queries with speculative majority may return uncommitted data
- Closed
-
SERVER-37560 Allow change streams to work with speculative majority reads
- Closed
-
SERVER-53247 Disable enableMajorityReadConcern:false
- Closed