Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-79349

Rename ShardVersion UNSHARDED to UNTRACKED

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Catalog and Routing

    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.

      Attachments

        Activity

          People

            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: