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

Using resume token from an 'invalidate' notification with 'resumeAfter' should error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.1, 4.1.1
    • Component/s: Querying
    • Labels:
      None

      Description

      After renaming a collection being watched, or renaming another collection to a collection being watched, it's possible to resume the change stream.

       

      This should probably produce an error instead.

       

      Also, note that we have tests which exercise this behavior, but don't assert that an error is thrown. These tests should be modified.

      jstests/change_streams/change_stream_rename_resumability.js
      jstests/change_streams/change_stream_rename_target.js 

       
      Edit (6/18):

      The desired behavior is to return an "invalidate" notification if resuming a change stream with a resume token from a command that would normally invalidate the stream. For example, resuming from the token of a collection drop notification on a single-collection change stream should return an "invalidate" then subsequently close the cursor. Resuming from the token of the invalidate notification itself should throw an error.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: