Clarify why createCollectionForApplyOps checks if currentName is on the same db as newName

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • TBD
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      In createCollectionForApplyOps, renameIntoRequestedNSSForApplyOps() asserts that if a collection with currentName and newCollName have the same UUID, they must be a part of the same database.

      It would be nice to clarify and/or revisit why this assertion is relevant, as the assertion was written nearly a decade ago.

              Assignee:
              Unassigned
              Reporter:
              Haley Connelly
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: