Skip to content

DOCSP-31907 - Add paragraph from server docs #460

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Oct 3, 2023
Merged

DOCSP-31907 - Add paragraph from server docs #460

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a7d2fac
Add paragraph from server docs
jordan-smith721 Oct 3, 2023
f7423c2
Removed 'should'
jordan-smith721 Oct 3, 2023
650d2c3
wording update
jordan-smith721 Oct 3, 2023
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
5 changes: 5 additions & 0 deletions source/fundamentals/crud/read-operations/change-streams.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,11 @@ Split Large Change Stream Events

Starting in MongoDB 7.0, you can use the ``$changeStreamSplitLargeEvent``
aggregation stage to split events that exceed 16 MB into smaller fragments.

Use ``$changeStreamSplitLargeEvent`` only when strictly necessary. For
example, use ``$changeStreamSplitLargeEvent`` if your application requires full
document pre- or post-images, and generates large events that exceed 16 MB.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I think "large" is redundant with "that exceed 16 MB."

Suggested change
document pre- or post-images, and generates large events that exceed 16 MB.
document pre- or post-images, and generates events that exceed 16 MB.


The $changeStreamSplitLargeEvent stage returns the fragments sequentially. You can
access the fragments by using a change stream cursor. Each fragment
includes a ``SplitEvent`` object containing the following fields:
Expand Down