[SERVER-30053] Get rid of the ShardingCatalogManager interface Created: 07/Jul/17  Updated: 30/Oct/23  Resolved: 17/Jul/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.9
Fix Version/s: 3.5.10

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-07-31
Participants:

 Description   

The ShardingCatalogManager interface is unnecessary since we never have a reason to override any of its functions. Because of this it should be removed.



 Comments   
Comment by Githook User [ 17/Jul/17 ]

Author:

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

Message: SERVER-30053 Get rid of the ShardingCatalogManager interface

As part of this change also moves ShardingCatalogManager to be a
decoration on ServiceContext and decouples the dependency between the
'connPoolStats' command and ShardingCatalogManager.
Branch: master
https://github.com/mongodb/mongo/commit/24e418966985b9bbaaa497f92dfbc69a2420e649

Comment by Githook User [ 13/Jul/17 ]

Author:

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

Message: SERVER-30053 Remove 'opCtx' parameter from Grid::catalogClient()

This method is now just a simple getter and doesn't require operation
context.
Branch: master
https://github.com/mongodb/mongo/commit/fc300ed58b943b93a3164103e4a767e3f81d1c3b

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