Details
-
Bug
-
Status: Closed
-
Minor - P4
-
Resolution: Works as Designed
-
4.4.0
-
None
-
None
-
ALL
-
Query 2020-10-19
Description
I tried creating a change stream with a start at operation time that is surely not in the oplog (1 second past epoch):
MongoDB Enterprise mongos> db.foo.watch([],{startAtOperationTime:Timestamp(1,0)})
|
This change stream appears to be accepted by the server without errors.
I expected to receive an error if I requested a start time that was not in the oplog.
Attachments
Issue Links
- related to
-
SERVER-32496 Start tailing from the beginning of changes history
-
- Backlog
-
-
SERVER-48523 Unconditionally check the first entry in the oplog when attempting to resume a change stream
-
- Closed
-