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

Rename fail with NamepsaceNotFound if target database does not exists yet

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Catalog and Routing
    • ALL
    • 3

      On sharded cluster, the rename collection command return NamespaceNotFound error if the target database does not exist. On replicaset the command will implicitely create the database.

            Assignee:
            Unassigned Unassigned
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: