-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
Currently, explain doesn't allow a custom default read concern to be applied. This is confusing because users might see plans that are different from the ones actually being executed. For example, shard filtering is not required for the "available" read concern.
- is related to
-
SERVER-21046 remove explain command readConcern ability
- Closed