Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-50903

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Works as Designed
    • Affects Version/s: 4.4.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Operating System:
      ALL
    • Sprint:
      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.

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bernard.gorman Bernard Gorman
              Reporter:
              oleg.pudeyev Oleg Pudeyev
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: