[SERVER-10214] New update logic does not honor 'timestamp(0)' fixups during object replacement. Created: 15/Jul/13  Updated: 02/Aug/18  Resolved: 18/Jul/13

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: None
Fix Version/s: 2.5.2

Type: Task Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

When updating an object with an object replacement (rather than a $mod), if the new object value contains a Timestamp(0) field in the first or second position, then the field is not reset to OpTime now as it should be.

This was the cause of the client tests failing when run with the new update codepath enabled.



 Comments   
Comment by auto [ 18/Jul/13 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}

Message: SERVER-10214 When doing an object replacement, update any 0 timestamps in first two fields
Branch: master
https://github.com/mongodb/mongo/commit/46a7a951f43dd20aa20937bbeed0584c9dd19485

Comment by auto [ 18/Jul/13 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@10gen.com'}

Message: SERVER-10214 Move OpTime out of db/repl and into bson
Branch: master
https://github.com/mongodb/mongo/commit/a64cbc9c0f2c98ea48a0efdaa431075e1912fe51

Generated at Thu Feb 08 03:22:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.