[SERVER-31243] No-op retry of a findAndModify upsert of a new document should return null with new=false Created: 25/Sep/17  Updated: 30/Oct/23  Resolved: 09/Nov/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.6.0-rc1
Fix Version/s: 3.6.0-rc4

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-11-13
Participants:

 Description   

If a findAndModify command with upsert=true inserted a new document and new=false, it will return null as the value. Currently, a retry of this command does not return null, like it should.

Failing retryable_writes_jscore_passthrough tests:

  • find_and_modify4.js
  • find_and_modify_empty_coll.js
  • find_and_modify_empty_update.js
  • find_and_modify_server6226.js


 Comments   
Comment by Githook User [ 09/Nov/17 ]

Author:

{'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}

Message: SERVER-31243 Make no-op retry of findAndModify upsert of new document return null with new=false

Also unblacklists find_and_modify_server6582.js from the retryable writes passthrough suite
Branch: master
https://github.com/mongodb/mongo/commit/d0ecca650c1f506db0cb6a4e58f0d0f112304b28

Generated at Thu Feb 08 04:26:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.