[SERVER-45126] Allow change stream to resume from the earliest oplog entry Created: 13/Dec/19  Updated: 06/Dec/22  Resolved: 17/Dec/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Davenson Lombard Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32496 Start tailing from the beginning of c... Backlog
Assigned Teams:
Query
Participants:
Case:

 Description   

The current implementation of change stream allow a user to:

  • Start a change stream from the latest oplog entry
  • Resume after or start after a resume token
  • Start at a timestamp

If we use a token that is not in the oplog or the timestamp is outside the oplog range, the change stream will fail.

Once a failure happens, the user will have to restart the change stream.

Proposition:

  • Add a method startAtFirst() which the MongoDB cluster would interpret as "start this change stream at the first oplog entry (oldest) that exists on a majority of nodes"

Thanks


Generated at Thu Feb 08 05:07:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.