[SERVER-29131] Support resumeAfter option to $changeNotication to control where to start returning notifications from, which always errors if no entry with the given resumeToken exists Created: 11/May/17  Updated: 30/Oct/23  Resolved: 08/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Crystal Horn Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-29504 Support resumeAfter behavior for shar... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-07-31, Repl 2017-08-21
Participants:

 Description   

If the first entry found in the oplog is greater than the token provided by the command, return an error that indicates that most likely the op that was requested has rolled off the back of the oplog.
If the first entry found in the oplog is less than the token provided by the command, but no entry with the exact token was found, then that means something is more seriously wrong - since we only return committed entries that can't roll back, such a scenario should be impossible



 Comments   
Comment by Githook User [ 10/Aug/17 ]

Author:

{'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto'}

Message: SERVER-29131 Support resumeAfter option to control where to start returning notifications from, which always errors if no entry with the given resumeToken exists
Branch: master
https://github.com/mongodb/mongo/commit/0686b1ed2d042ad5adb671912e7d6b9cc89d0c4f

Comment by Matthew Russotto [ 08/Aug/17 ]

Documentation/Driver changes for this issue are part of those for the whole feature.

Generated at Thu Feb 08 04:19:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.