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

Don't allow resuming changeStreams after sharded collection drop

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-09-11, Repl 2017-10-02, Repl 2017-10-23

      Once a collection is dropped we lose all catalog information about it, which makes it impossible to extract the shard key on new cursors on sharded collections. So that means that resuming a sharded change stream after the collection was dropped won't work. We should make sure that fails gracefully.

            Assignee:
            nathan.myers Nathan Myers
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: