Loading...

XML

Word

Printable

JSON

Type: New Feature
Resolution: Done
Priority: Major - P3
Fix Version/s: 4.3.1
Affects Version/s: None
Component/s: Querying
Labels:
- query_triage

Backwards Compatibility:
Fully Compatible
Sprint:
Query 2019-10-07
Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

SERVER-4716 reexamine scan and order memory limit handling

Closed

SERVER-3867 aggregation: use external sort to handle larger sorts

Closed

related to

SERVER-9444 Use new Sorter for Aggregation $sort and $group

Closed

SERVER-23768 Document internalQueryExecMaxBlockingSortBytes in config.yaml

Closed

SERVER-43683 Make find command with allowDiskUse option work against a view

Closed

(3 related to)

Assignee:: David Storch
Reporter:: Aaron Staple (Inactive)
Participants:: Aaron Staple, Daniel Pasette, David Storch, Eliot Horowitz, Githook User, Jeffrey Yemin, Luke Thompson
Votes:: 12 Vote for this issue
Watchers:: 28 Start watching this issue

Created:: Nov 16 2012 08:55:15 PM UTC
Updated:: Oct 09 2019 05:26:15 PM UTC
Resolved:: Oct 02 2019 12:42:13 AM UTC
Confidence Status Last Update:: 25/Sep/19 4:34 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates