-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
ExpressionContext::getNeedsMerge() is currently overloaded to mean $group accumulators need to output partial results and that $sortKey should be populated. SERVER-103724 replaced the needsMerge bit on the ExpressionContext with an enum that allows us to differentiate these cases (the wire protocol still uses booleans).
This ticket represents the work to audit all callers of getNeedsMerge() and replace them with a check for sorted/unsorted merge. Then we can remove the getNeedsMerge() function entirely.
- is related to
-
SERVER-103724 $sort-$project query on a sharded collection can assert on merging node
-
- In Progress
-