Skip to content

Commit 6183d86

Browse files
committed
rr and jm feedback
1 parent e9aab32 commit 6183d86

File tree

3 files changed

+10
-10
lines changed

3 files changed

+10
-10
lines changed

source/includes/extracts-watch-option.yaml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,15 @@
11
ref: watch-option-batchSize
22
content: |
3-
The maximum number of documents within each batch returned in a query result, which applies
3+
The maximum number of documents within each batch returned in a change stream, which applies
44
to the ``aggregate`` command. By default, the ``aggregate`` command has an initial batch size of
55
``101`` documents and a maximum size of 16 mebibytes (MiB) for each subsequent batch. This
66
option can enforce a smaller limit than 16 MiB, but not a larger one. If you set ``batchSize``
77
to a limit that results in batches larger than 16 MiB, this option has no effect.
8+
9+
Irrespective of the ``batchSize`` option, the initial ``aggregate`` command
10+
response for a change stream generally does not include any documents
11+
unless another option is used to configure its starting point (e.g.
12+
``startAfter``).
813
---
914
ref: watch-option-fullDocument
1015
content: |

source/reference/method/MongoDBCollection-find.txt

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -52,15 +52,14 @@ Parameters
5252

5353
* - batchSize
5454
- integer
55-
- The maximum number of documents to return in the first batch. By default, the ``find()``
56-
command has an initial batch size of ``101`` documents. This
57-
option can enforce a smaller limit than 16 mebibytes (MiB), but not a larger
55+
- The maximum number of documents within each batch returned in a query result. By default, the ``find``
56+
command has an initial batch size of ``101`` documents and a maximum size of 16 mebibytes (MiB)
57+
for each subsequent batch. This option can enforce a smaller limit than 16 mebibytes (MiB), but not a larger
5858
one. If you set ``batchSize`` to a limit that results in batches larger than
5959
16 MiB, this option has no effect.
6060

6161
A batchSize of ``0`` means that the cursor will be established, but no documents
62-
will be returned in the first batch. This may be useful for quickly returning a cursor
63-
or failure without doing significant server-side work.
62+
will be returned in the first batch.
6463

6564
Unlike the previous wire protocol version, a batchSize of ``1`` for the
6665
:dbcommand:`find` command does not close the cursor.

source/reference/method/MongoDBCollection-listSearchIndexes.txt

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,6 @@ Parameters
4747
one. If you set ``batchSize`` to a limit that results in batches larger than
4848
16 MiB, this option has no effect.
4949

50-
A batchSize of ``0`` means that the cursor will be established, but no documents
51-
will be returned in the first batch. This may be useful for quickly returning a cursor
52-
or failure from ``aggregate`` without doing significant server-side work.
53-
5450
* - codec
5551
- MongoDB\\Codec\\DocumentCodec
5652
- .. include:: /includes/extracts/collection-option-codec.rst

0 commit comments

Comments
 (0)