Skip to content

$orderby should have warning for 32MB limit #1556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions source/reference/operator/meta/orderby.txt
Original file line number Diff line number Diff line change
Expand Up @@ -35,3 +35,12 @@ $orderby
large in-memory sort. The :method:`cursor.limit()` increases the
speed and reduces the amount of memory required to return this query
by way of an optimized algorithm.

.. warning::

The sort function requires that the entire sort be able to
complete within 32 megabytes. When the sort option consumes more
than 32 megabytes, MongoDB will return an error. Use :operator:`$maxScan`
and/or :method:`~cursor.limit()`, or create an index on the field that you're
sorting to avoid this error.