Temporarily rename sharded metadata without a transaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Sharding 2021-01-25
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As long as SERVER-53871 is not completed, rely on the catalog client to perform metadata rename operations.

      Get also rid of the new epoch logic since it has been decided to not change a collection's epoch upon rename.

            Assignee:
            Pierlauro Sciarelli
            Reporter:
            Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: