-
Type: Bug
-
Resolution: Unresolved
-
Priority: Critical - P2
-
None
-
Affects Version/s: 2.6.0-rc1
-
Query Optimization
-
ALL
I think it needs to both set QueryPlannerParams::INCLUDE_SHARD_FILTER and either use a ClientCursor or a RangePreserver.
- is related to
-
SERVER-42160 $group stages that use a DISTINCT_SCAN do not use a SHARDING_FILTER on sharded collections
- Backlog
- related to
-
SERVER-3645 Sharded collection counts (on primary) can report too many results
- Closed