[SERVER-60555] Get rid of CollectionShardingState/Runtime::get_UNSAFE Created: 08/Oct/21  Updated: 29/Oct/23  Resolved: 11/Oct/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.2.0

Type: Improvement Priority: Minor - P4
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-10-18
Participants:

 Description   

The CollectionShardingState/Runtime::get_UNSAFE calls seem to have been added just for a single unit-test and they seem very tempting for someone to find a creative use. We should throw them out and instead just acquire lock in the unit-test.



 Comments   
Comment by Githook User [ 11/Oct/21 ]

Author:

{'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}

Message: SERVER-60555 Get rid of CollectionShardingState/Runtime::get_UNSAFE
Branch: master
https://github.com/mongodb/mongo/commit/8be03e014addf0252d718ed329ab8d5235e0fdec

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