Use different exception for collection namespace already in use.

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Declined
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      In several places we are throwing Write Conflict Exception for scenarios where the 'collection namespace is already in use'. Those are unrelated to storage engine Write Conflicts. We should use a different error code and handling policy on those situations.

      • collection_catalog.cpp::_ensureNamespaceDoesNotExist (here, here and here)
      • database_impl.cpp::_checkCanCreateCollection (here) and corresponding checkpoint (here)
      • database_impl.cpp::_createCollection (here)

            Assignee:
            Unassigned
            Reporter:
            Ernesto Rodriguez Reina
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: