applyOps collMod handling should only allow nonexistent UUIDs for UUID upgrade collMods

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.12
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • Storage 2017-08-21
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, a collMod oplog entry with a nonexistent UUID will be applied to an existing collection if the collection name of the oplog entry matches an existing collection name. This is due to the handling of collMods that are used to upgrade from 3.4 to 3.6 and add UUIDs to collections. This special handling should only occur for collMods that are for upgrade, i.e., empty collMods.

            Assignee:
            Maria van Keulen
            Reporter:
            Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: