[DOCS-11828] Docs for SERVER-35030: Add 'startAfter' option to the $changeStream stage Created: 21/Jun/18  Updated: 29/Oct/23  Resolved: 04/Oct/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 4.1.1

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Isabella Siu (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-35030 Add 'startAfter' option to the $chang... Closed
Duplicate
Related
is related to DOCS-12013 Docs for SERVER-36899: Parse and acce... Closed
Participants:
Days since reply: 5 years, 18 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

----------------------------

Original Description

Description:

No documentation summary in engineering ticket

Engineering Ticket Description:

Similar to 'resumeAfter', this option takes a resume token and starts a new change stream returning the first notification after the token.

This will allow users to watch collections that have been dropped and recreated or newly renamed collections without missing any notifications.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Githook User [ 09/Oct/18 ]

Author:

{'name': 'Isabella Siu', 'email': 'isabellasiu@Isabellas-MacBook.local'}

Message: DOCS-11828 document 'startAfter' option for $changeStream
Branch: master
https://github.com/mongodb/docs/commit/7abd68d0635c572200648132abf611f2a4ae5fa3

Comment by Githook User [ 03/Oct/18 ]

Author:

{'name': 'Isabella Siu', 'email': 'isabellasiu@Isabellas-MacBook.local'}

Message: DOCS-11828 document 'startAfter' option for $changeStream
Branch: upcoming-4.2
https://github.com/mongodb/docs/commit/791bca6a2c00c3e313027b741feb98aa0f6802db

Generated at Thu Feb 08 08:03:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.