Upsert behaving differently on clustered collections compared with regular

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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
            Reporter:
            Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: