Use donor specs for _id index in tenant migration collection cloner

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc2, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • ALL
    • v5.0
    • Repl 2021-06-14
    • 36
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the tenant migration cloner, we separate the _id index from other index builds. We rely on the createCollection code path to build the _id index with default specs, whereas for other indexes, we will use the specs from the donor.

      Because of this, if the user specifies v: 1 for their index builds, it seems possible for there to be a mismatch between the versions. Since there is a semantic difference between v:1 and v:2 indexes, we should use the user's specs when building the _id index.

              Assignee:
              Vishnu Kaushik
              Reporter:
              Xuerui Fa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: