[SERVER-51006] Make the CatalogCache not return ShardRegistry concepts as part of its public API Created: 17/Sep/20 Updated: 29/Oct/23 Resolved: 18/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.8.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2020-09-21 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Currently, the CatalogCache returns a reference to Shard objects, which are ShardRegistry concepts. With the introduction of the VectorClock, we should go in the direction of decoupling them. This ticket is about removing these references, because they are not used anywheree. |
| Comments |
| Comment by Githook User [ 18/Sep/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |