[SERVER-18055] Move legacy config server upgrade to the legacy catalog manager Created: 14/Apr/15  Updated: 19/Sep/15  Resolved: 15/Apr/15

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2 04/24/15
Participants:

 Description   

The config server upgrade code is currently specific to the legacy catalog manager and should go in the same library.



 Comments   
Comment by Githook User [ 15/Apr/15 ]

Author:

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

Message: SERVER-18055 Move config server schema upgrade under the legacy catalog manager

The current upgrade code only applies to the legacy config metadata so it
is best if it resides under the legacy catalog manager.
Branch: master
https://github.com/mongodb/mongo/commit/0a93c411a6a22c0dac8a82fed0efc4e60f62f40d

Generated at Thu Feb 08 03:46:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.