Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-61486

Investigate work needed to track duplicate key violations before unique index conversion time

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2021-11-29, Execution Team 2021-12-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It's a requirement for the index conversion time to be relative to the number of violations instead of the size of the index itself.

      This ticket should look into reusing the DuplicateKeyTracker to keep track of uniqueness violations instead of relying on a full index scan.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None