-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
(copied to CRM)
Hi Team,
Customer was referencing this github doc to configure changestream to start from the beginning.
Using `startAtOperation` option, this doc mentions the use of timestamp (`0`) allows you to to start at the beginning of the oplog which isn't guarantee to work once the oplog rolls over for the first time. Once the oplog rolls over, it cannot report those events that have fallen off, so it will error. If you specify a timestamp that is still inside the oplog, then it can return all the events according to your request without missing anything
Further discussion in this slack thread
Support Case - 01181040
Requested Action.
- Looking to update this doc to mention this caveat or to remove it.