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

      When cloning the collection, the original instance is not used.
      createNewCollection(opCtx, readTimestamp, *catalogEntry) --> initFromExisting(..., /*collection=*/nullptr, ...) 
      Creating from scratch from the mdb catalog entry ends up calling storageEngine->markIdentInUse() for each index, which only searches drop pending idents.
      Under normal circumstances the index is usually not drop pending, so nothing is found and the cloning fails. Upstream this is interpreted as "decided to not clone".

      Basically this means cloning only works for clustered collections with no secondary indexes.

            Assignee:
            Unassigned
            Reporter:
            Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: