-
Type:
New Feature
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
Fully Compatible
-
Query 2019-10-07
-
(copied to CRM)
Right now when query results must be sorted before being returned, a top-N sort is performed in memory with a memory footprint cap enforced. The goal for this ticket is move to external sorting if too much memory is required, see discussion in SERVER-4716.
- depends on
-
SERVER-6157 Refactor BSONObjExtSort
-
- Closed
-
- is depended on by
-
SERVER-7676 find usings sort,skip,limit where sort is on an unindexed attribute produces an error when executed from mongos command prompt but works correctly from mongod command prompt.
-
- Closed
-
- is duplicated by
-
SERVER-5374 batchSize is a hard limit for an in memory sort
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-9444 Use new Sorter for Aggregation $sort and $group
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-