Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
Component/s: None
Labels:
- qexec-team

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.4
Sprint:
Query 2020-04-20, Query 2020-05-04, Query 2020-05-18
Case:
Linked BF Score:
33
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

As of ~~SERVER-37124~~, this behavior is true for update commands and should be extended to be true for findAndModify as well. See the linked ticket for more details.

causes

SERVER-95523 upsert does not handle DuplicateKey retry correctly

Closed

clones

SERVER-59758 findAndModify with upsert=true generates duplicate key errors

Closed

is duplicated by

SERVER-59758 findAndModify with upsert=true generates duplicate key errors

Closed

SERVER-60252 `findAndModify` does not retry on unique index violations

Closed

related to

SERVER-51354 Complete TODO listed in SERVER-47212

Closed

SERVER-14322 Retry on predicate unique index violations of update + upsert -> insert when possible

Closed

SERVER-37124 Retry full upsert path when duplicate key exception matches exact query predicate

Closed

(2 related to)

Assignee:: Svilen Mihaylov (Inactive)
Reporter:: Gregory Noma
Participants:: Githook User, Gregory Noma, Svilen Mihaylov
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Mar 31 2020 07:32:15 PM UTC
Updated:: Oct 04 2024 01:08:34 AM UTC
Resolved:: May 07 2020 06:06:01 PM UTC
Confidence Status Last Update:: 29/Apr/20 6:44 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates