[SERVER-83499] Update metadata manager tests that expect a collection description to hold a range preserver Created: 21/Nov/23  Updated: 22/Nov/23  Resolved: 22/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 7.0.2
Fix Version/s: 7.0.5

Type: Bug Priority: Major - P3
Reporter: Allison Easton Assignee: Allison Easton
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
is caused by SERVER-79780 ScopedCollectionDescription shouldn't... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: CAR Team 2023-11-27
Participants:
Linked BF Score: 5

 Description   

7.0 only.

In SERVER-79780, the getActiveMetadata function in the metadata manager was changed to add a boolean representing whether the range should be preserved. However, when backporting this to 7.0, some of the tests were not updated and so are using getActiveMetadata without getting a rangePreserver but expecting the range to be preserved.

This ticket is to look through the metadata manager unit tests and see if any of them require preserveRange to be true (CleanupNotificationsAreSignaledWhenMetadataManagerIsDestroyed definitely does).



 Comments   
Comment by Githook User [ 22/Nov/23 ]

Author:

{'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}

Message: SERVER-83499 Update metadata manager tests that expect a collection description to hold a range preserver
Branch: v7.0
https://github.com/mongodb/mongo/commit/2ab0f89a51fc355533b900698623dd34ffa0a4c2

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