- Reference >
- Database Commands >
- Query and Write Operation Commands >
- getMore
getMore¶
On this page
Definition¶
Syntax¶
The getMore
command has the following form:
Command Fields¶
The command accepts the following fields:
Field | Type | Description |
---|---|---|
getMore |
long | The cursor id. |
collection |
string | The name of the collection over which the cursor is operating. |
batchSize |
positive integer | Optional. The number of documents to return in the batch. |
maxTimeMS |
non-negative integer | Optional. Specifies a time limit in milliseconds for processing
operations on a cursor. If you do not specify a value for maxTimeMS,
operations will not time out. A value of MongoDB terminates operations that exceed their allotted time limit
using the same mechanism as |
comment |
any | Optional. A user-provided comment to attach to this command. Once set, this comment appears alongside records of this command in the following locations:
A comment can be any valid BSON type (string, integer, object, array, etc). New in version 4.4. |
Output¶
The command returns a document that contains the cursor information as well as the next batch.
For example, a document similar to the one below may be returned when
getMore
is run on a cursor that was originally created by a
find
operation on a sharded cluster:
Field | Description |
---|---|
cursor |
Contains the cursor information, including the
cursor id as well as the Starting in 4.4, if the cursor from a If the queried shards are initially available for the
|
"ok" |
Indicates whether the command has succeeded (1 ) or failed
(0 ). |
In addition to the aforementioned getMore
-specific fields,
the db.runCommand()
includes the following information for
replica sets and sharded clusters:
$clusterTime
operationTime
See db.runCommand() Results for details.
Behavior¶
Access Control¶
New in version 3.6.
If authentication is turned on, you can
only issue a getMore
against cursors you created.