mongos returns inconsistent error code when renameCollection target already exists

XMLWordPrintableJSON

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

      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
              Reporter:
              Wenbin Zhu
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: