No error when change stream's startAtOperationTime is not in oplog

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Works as Designed
    • Priority: Minor - P4
    • None
    • Affects Version/s: 4.4.0
    • Component/s: None
    • ALL
    • Query 2020-10-19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

      SO inquiry: https://stackoverflow.com/questions/63860124/how-to-check-if-theres-enough-oplog-history-for-a-change-stream-start-position/63861498#comment112943453_63861498

            Assignee:
            Bernard Gorman
            Reporter:
            Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: