Adapt convertToCapped and cloneToCapped command to work with tracked unsharded collection

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently these commands do not properly update the sharding catalog and do not take into account that the collection could actually leave in a shard different from the DB primary.

              Assignee:
              [DO NOT USE] Backlog - Catalog and Routing
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: