Handle old keystring formats in unique indexes for extra keys check

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Due to the setting of the keystring with the record ID as nextLookupStart, older keystrings with the old format (_id index also follows the old format) may result in skipping a key when starting the next batch upon calling indexCursor->seekForKeyString(opCtx, lookupStart).

       

            Assignee:
            Unassigned
            Reporter:
            Moustafa Maher
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: