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

Upsert behaving differently on clustered collections compared with regular

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2023-02-20, Execution Team 2023-02-06, Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03

      When upsert fallback to insert it can cause a DuplicateKey error thrown to the user if there's another concurrent insert/upsert on the same key when the collection is clustered.

      Should upsert retry the update when encountering DuplicateKey?

            Assignee:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: