[SERVER-46205] Remove the direct dependency of CollectionShardingState on CatalogCache/ChunkManager Created: 16/Feb/20  Updated: 06/Dec/22  Resolved: 17/Feb/22

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-46204 Implement the facade of the Filtering... Closed
depends on SERVER-46206 Make the FilteringMetadataService par... Closed
depends on SERVER-46207 Make the CatalogCache efficiently pro... Closed
depends on SERVER-46208 Remove the ShardServerCatalogCacheLoa... Closed
depends on SERVER-46209 Ensure all sharding consumers are abl... Closed
Duplicate
Assigned Teams:
Sharding EMEA
Participants:

 Description   

The work for SERVER-32198 will decouple the direct dependency of non-sharding code on CollectionMetadata and all the interactions of non-sharding consumers with sharding will be going only through CollectionShardingState and specifically through the getOwnershipFilter and getCollectionDescription interfaces.

This work in this ticket is one level below the CollectionShardingState implementation on shards and is to remove all dependencies from CollectionShardingState on CollectionMetadata and push that interaction to be done through calls to the FilteringMetadataService.

After this ticket is done, there should be no more CollectionMetadata calls and the MetadataManager can be thrown out.


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