Investigate changes in PM-1966: Track views in the catalog

    • Type: Investigation
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None

      Original Downstream Change Summary

      Backup will be impacted

      Description of Linked Ticket

      Epic Summary

      Summary

      Move tracking of views from the primary shard for a database, to the catalog, and make view definitions available on mongos

      Motivation

      The status quo, where views are tracked on the primary shard for their database, has a few downsides:

      • View definitions require an extra round trip to resolve
      • Query doesn't have access to the full universe of namespaces on routers
      • Views living on the primary shard for a database necessitates the continued existence of primary shards for databases

      Moving view definitions will solve those problems, improving performance, ability to perform query planning and removing a barrier to getting rid of the notion of primary shards (and in turn removing a barrier to removing the movePrimary command)

      Cast of Characters

      • Product Owner:
      • Project Lead:
      • Program Manager:
      • Drivers Contact:

      Documentation

      Scope Document
      Technical Design Document
      Product Description
      Docs Update

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: