Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14469

Investigate changes in SERVER-56296: Uniform `fromNss == toNss` rename behavior between rs and sharded cluster

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 5.0.0-rc1, 5.1.0-rc0
    • manual, Server
    • None

    Description

      Description

      Downstream Change Summary

      Just for the record, don't know if the corner case was taken into account previously.

      If a user tries to rename a collection to itself, starting from now an IllegalOperation is thrown. Before, a misleading NamespaceNotFound exception was thrown.

      Description of Linked Ticket

      If the collection exists, the collection version must be returned in a best-effort fashion, without acquiring any lock.

      If the collection exists but dropTarget=true, an `IllegalOptions` error must be returned.

      If the collection doesn't exist, a `NamespaceNotFound` error is already thrown both in case of RS or sharded cluster.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          backported by

          Task - A task that needs to be done. DOCS-14499 [BACKPORT] [v5.0] Uniform `fromNss == toNss` rename behavior between rs and sharded cluster

          • Major - P3 - Major loss of function.
          • Closed
          documents

          Task - A task that needs to be done. SERVER-56296 Uniform `fromNss == toNss` rename behavior between rs and sharded cluster

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              naomi.pentrel@mongodb.com Naomi Pentrel (Inactive)
              backlog-server-pm Backlog - Core Eng Program Management Team
              Jess Mokrzecki Jess Mokrzecki
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                1 year, 49 weeks, 3 days ago