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

[3.6] Change streams on a non-existent collection are invalidated by a database drop

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Works as Designed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Aggregation Framework
    • None
    • Query
    • ALL

    Description

      As part of 4.0, we added change streams notifications for database drops and consciously decided that single-collection change streams should remain open if the collection never existed (some discussion in the review for SERVER-35029).

      This is different behavior in 3.6 as the single-collection change streams are invalidated if the database is dropped. We should decide on a consistent approach and document it.

      Attachments

        Activity

          People

            backlog-server-query Backlog - Query Team (Inactive)
            nicholas.zolnierz@mongodb.com Nicholas Zolnierz
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: