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

Refactor collection creation idempotency to use single collection acquisition

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing
    • 2

    Description

      Currently, the mechanism that provides idempotency for creating a collection acquires the collection to check its options after receiving a NamespaceExists error from the creation attempt. This means that there are two separate acquisitions that occur: once to try to create the collection, and once to check if the existing options are the same (with the collection being released in between). We may want to refactor this so that all of this can happen under a single collection acquisition.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: