Do not allow a collection to be created with the UUID of an existing collection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • ALL
    • Execution Team 2019-08-12
    • 51
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      There are no assertions, invariants, or errors thrown in DatabaseImpl::createCollection if a collection is created using the UUID of a collection that already exists in the UUIDCatalog.

      Creating a new collection with an existing UUID results in theĀ UUIDCatalog::onCreateCollection observer removing the entry of the previous collection. This allows two collections to exist with the same UUID. In the case of two-phase collection drops, this can result in no collections registered to a UUID, despite existing.

            Assignee:
            Daniel Gottlieb (Inactive)
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: