[SERVER-53113] Unit test CollectionCatalog copy-on-write and CollectionCatalogStasher Created: 30/Nov/20  Updated: 29/Oct/23  Resolved: 06/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-12-28, Execution Team 2021-01-11
Participants:

 Description   

Testing either of these things requires setting up the unit test different than is done currently in collection_catalog_test.cpp. Rather than a single CollectionCatalog 'catalog' created for the unit tests, we need to create and set a CollectionCatalog on the ServiceContext and fetch it from there, so that copy-on-writes can change it and the test can fetch a new instance that's updated.



 Comments   
Comment by Githook User [ 06/Jan/21 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-53113 Add unittests for writing to the CollectionCatalog using read-copy-update.
Branch: master
https://github.com/mongodb/mongo/commit/d81baa7d807ad7c62de0e9f2e72390aad428e105

Generated at Thu Feb 08 05:29:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.