[SERVER-12915] update must keep track of all modified docs, even if they don't move Created: 26/Feb/14  Updated: 11/Jul/16  Resolved: 26/Feb/14

Status: Closed
Project: Core Server
Component/s: Write Ops
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: hari.khalsa@10gen.com Assignee: hari.khalsa@10gen.com
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

t.drop();
 
t.save( { x : 1 } );
t.save( { x : 2 } );
t.save( { x : 3 } );
 
t.ensureIndex( { x : 1 } );
t.update( { x : { $gt : 0 } } , { $inc : { x : 5 } } , false , true );

Participants:

 Description   

Otherwise we'll continually update the same document. Our jstest for this didn't catch the issue because it used to use a collection scan for the underlying query execution.



 Comments   
Comment by Githook User [ 26/Feb/14 ]

Author:

{u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}

Message: SERVER-12915 only track modified docs if move or mods affect indices
Branch: master
https://github.com/mongodb/mongo/commit/3709484b65d0c153d4d52713e8466b7b3a791233

Comment by Githook User [ 26/Feb/14 ]

Author:

{u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}

Message: SERVER-12915 update must keep track of updated locs even w/in-place updates
Branch: master
https://github.com/mongodb/mongo/commit/4c599a895994cc32593b68b84b79f42f9c6c348c

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