[SERVER-79349] Rename ShardVersion UNSHARDED to UNTRACKED Created: 26/Jul/23  Updated: 26/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Catalog and Routing
Participants:

 Description   

Today the special UNSHARDED chunk version constant is used to represent collections that are not registered in the sharding catalog. When a collection does not have an entry in config.collections it means it is either unsharded or do not exist yet.

In the context of PM-3364 we are going to track unsharded collection in the sharding catalog, in particular unsharded collection will have a routing table with only one chunk, this means that they will also have a shard/collection version.

Thus, we should rename the UNSHARDED version to UNTRACKED to reflect the fact that this version now represent collections that are not present in the sharding catalog. In these cases, the collection could be either a special collection (a view or a system collection) or a collection that does not exist yet.


Generated at Thu Feb 08 06:40:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.