[SERVER-10489] Move okForStorage checks till after in-mem update, but before persistence Created: 12/Aug/13  Updated: 11/Jul/16  Resolved: 14/Nov/13

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

Type: Task Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: okForStorage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-10338 Create okForStorage mutable::document... Closed
Participants:

 Description   

Currently it is possible to update a bad document and for it stay bad (invalid) after the update since we don't check okForStorage on the mutated document.



 Comments   
Comment by Githook User [ 14/Nov/13 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-10489: move collection creation after validation for upsert case
Branch: master
https://github.com/mongodb/mongo/commit/9a28a092d50eeb1bd45815b256f0180044a5c588

Comment by Githook User [ 14/Nov/13 ]

Author:

{u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}

Message: SERVER-11531, SERVER-10489, SERVER-6835, SERVER-4830: Refactor update system to support immutable fields, consolodate storage validation, and misc issues.
Branch: master
https://github.com/mongodb/mongo/commit/b98712c551e8ab27c33e1a5e7c694fa36c3334ce

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