Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11901

Docs for SERVER-34789: Using resume token from an 'invalidate' notification with 'resumeAfter' should error

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.0.1, 4.1.1
    • Affects Version/s: None
    • Component/s: None
    • Labels:


      Original Description


      Not certain if this is needed, but deferring to Docs team for it.

      Engineering Ticket 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.


      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.



      Scope of changes (files that need work and how much)

      Since we currently already tell our users:
      You cannot resume a change stream after an invalidate event (for example, a collection drop or rename) closes the stream.

      Will use to update the drop/dropCollection/renameCollection (+shell helpers) that they create invalidate events for change streams.

      Impact to other docs outside of this product

      MVP (work and date?)

      Resources (e.g. Scope Docs, Invision)

            Unassigned Unassigned
            kay.kim@mongodb.com Kay Kim (Inactive)
            0 Vote for this issue
            1 Start watching this issue

              5 years, 40 weeks, 2 days ago