-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
None
-
Query Optimization
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
It looks like we do know whether an aggregate needs to be merged on a shard (here) before we set the batchSize (in this function, here). If we pass that value through to the function, we may be able to eliminate the need for a request to be sent with batchSize: 0
- is related to
-
SERVER-38761 Explore options for batch size when gathering shard results
-
- Backlog
-
-
SERVER-45738 Sharded find operations wait for an entire batch to be generated before retrying on stale shard version errors
-
- Backlog
-