Refuse to start up mongod 4.0 unless all collections have UUIDs

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.3
    • Affects Version/s: None
    • Component/s: Upgrade/Downgrade
    • None
    • Fully Compatible
    • Storage 2018-02-26
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In 4.0, it is assumed all collections have UUIDs. To ensure no potential 3.4-3.6 related UUID assignment bugs carry over into 4.0 once a user upgrades, all collections should be checked on startup for UUIDs and mongod should fail to start up unless all collections have UUIDs.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Maria van Keulen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: