- Reference >
mongosh
Methods >- Cursor Methods >
- cursor.max()
cursor.max()¶
On this page
Definition¶
-
cursor.
max
()¶ Important
mongosh
MethodThis page documents a
mongosh
method. This is not the documentation for a language-specific driver such as Node.js.For MongoDB API drivers, refer to the language-specific :driver:`MongoDB driver documentation </>`.
For the legacy
mongo
shell documentation, refer to the documentation for the corresponding MongoDB Server release:Specifies the exclusive upper bound for a specific index in order to constrain the results of
find()
.max()
provides a way to specify an upper bound on compound key indexes.
Parameters¶
The max()
method has the following parameter:
Parameter | Type | Description |
---|---|---|
indexBounds |
document | The exclusive upper bound for the index keys. |
The indexBounds
parameter has the following prototype form:
The fields correspond to all the keys of a particular index in order.
Note
Index Use
Starting in MongoDB 4.2, you must explicitly specify the particular
index with the hint()
method to run
max()
with the following exception: you do not
need to hint if the find()
query is an
equality condition on the _id
field { _id: <value> }
.
In previous versions, you could run max()
with or
without explicitly hinting the index regardless of the query
condition. If run without the hint in 4.0 and earlier, MongoDB
selects the index using the fields in the indexBounds
; however,
if multiple indexes exist on same fields with different sort orders,
the selection of the index may be ambiguous.
See also
max()
exists primarily to support the
mongos
(sharding) process.
Behavior¶
Interaction with Index Selection¶
Because max()
requires an index on a field,
and forces the query to use this index, you may prefer the
$lt
operator for the query if possible. Consider the
following example:
The query will use the index on the price
field, even if
the index on _id
may be better.
Index Bounds¶
max()
without min()
¶
The min()
and max()
methods
indicate that the system should avoid normal query planning. They
construct an index scan where the index bounds are explicitly specified
by the values given in min()
and
max()
.
Warning
If one of the two boundaries is not specified, the query plan will be an index scan that is unbounded on one side. This may degrade performance compared to a query containing neither operator, or one that uses both operators to more tightly constrain the index scan.
Example¶
Note
Starting in MongoDB 4.2, you must explicitly specify the particular
index with the hint()
method to run
max()
with the following exception: you do not
need to hint if the find()
query is an
equality condition on the _id
field { _id: <value> }
.
For the examples below, create a sample collection named products
that holds the
following documents:
Create the following indexes for the collection:
Using the ordering of
{ item: 1, type: 1 }
index,max()
limits the query to the documents that are below the bound ofitem
equal toapple
andtype
equal tojonagold
:The query returns the following documents:
Using the ordering of the index
{ price: 1 }
,max()
limits the query to the documents that are below the index key bound ofprice
equal toNumberDecimal("1.99")
andmin()
limits the query to the documents that are at or above the index key bound ofprice
equal toNumberDecimal("1.39")
:Note
Starting in MongoDB 4.0, the bound specified by
max()
must be greater than the bound specified bymin()
.The query returns the following documents: