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

Source and target database primary shards should match when renaming unsharded collections

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual, Server
    • Labels:

      Description

      Description

      The renameCollection documentation is not mentioning a current limitation in sharded clusters: it is not supported the rename of an unsharded collection if source and target database primary shards are different.

      There is also a test showing that this scenario is expected to fail.

      The following sentence should be reformulated.

      FROM:
      "You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster."

      TO something like:

      "You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard."

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            pierlauro.sciarelli Pierlauro Sciarelli
            Participants:
            Last commenter:
            Andrew Feierabend
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Days since reply:
              4 weeks, 3 days ago