[DOCS-9187] upsert is not atomic Created: 21/Oct/16 Updated: 13/Apr/21 Resolved: 13/Apr/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Andrew Feierabend (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 2 years, 43 weeks, 1 day ago | ||||||||
| Epic Link: | DOCSP-11701 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
Our documentation for update and findAndModify mention atomicity but don't caveat that only existing documents can be atomically modified. upsert operations are not atomic and can result (among other things) in duplicates or duplicate key errors. (See The documentation should clearly warn users about this potential problem with upserts. h/t to john.l.page@mongodb.com and rassi for highlighting this issue in the driver team slack channel |
| Comments |
| Comment by Githook User [ 13/Apr/21 ] |
|
Author: {'name': 'Andrew Feierabend', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}Message: DOCSP-15179- |
| Comment by Githook User [ 13/Apr/21 ] |
|
Author: {'name': 'Andrew Feierabend', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}Message: DOCSP-15179- |
| Comment by Githook User [ 13/Apr/21 ] |
|
Author: {'name': 'Andrew Feierabend', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}Message: DOCSP-15179- |