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

mongos returns inconsistent error code when renameCollection target already exists

    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Sharding EMEA 2022-05-02

      If a rename finds that the target namespace exists, we expect mongod and mongos to return NamespaceExists error, but with mongos, depending on if the target is a sharded collection, it sometimes returns NamespaceExists error as expected, but sometimes returns an error without a dedicated error code.

            Assignee:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Reporter:
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: