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

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

    XMLWordPrintableJSON

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.

      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

          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-32496 Start tailing from the beginning of changes history

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Backlog

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-48523 Unconditionally check the first entry in the oplog when attempting to resume a change stream

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              bernard.gorman@mongodb.com Bernard Gorman
              oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: