[SERVER-28620] Remove the oplogHack logic in WiredTiger glue code Created: 04/Apr/17  Updated: 09/Sep/20  Resolved: 22/Aug/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.5.13

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

Attachments: PDF File Design_ Storage API Changes to use timestamps.pdf    
Issue Links:
Depends
Related
is related to SERVER-50824 Revisit WriteConflictException TODO w... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage 2017-05-29, Storage 2017-06-19, Storage 2017-07-10, Storage 2017-07-31, Storage 2017-08-21, Storage 2017-09-11
Participants:
Linked BF Score: 15

 Description   

and confirm the oplog visibility rules are not broken.



 Comments   
Comment by Githook User [ 22/Aug/17 ]

Author:

{'username': 'milkie', 'email': 'milkie@10gen.com', 'name': 'Eric Milkie'}

Message: SERVER-28620 Adorn all oplog writes with timestamps

These timestamps are now used to implement oplog visibility rules, in place of the current
in-memory vector of uncommitted ops that the WiredTiger glue code currently uses.
This change also introduces a TimestampedBSONObj class, which encapsulates a BSONObject with its
associated write timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/77dc6917428ffad4b9ff2d54d78fa9b225f78a4b

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