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

Allow calling executeCommandAgainstDatabasePrimary using CollectionRoutingInfo

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Catalog and Routing

      The executeComandAgainstDatabasePrimary function takes in a CachedDatabaseInfo object in order to route the command. If the caller is using a CollectionRouter loop, though, then they have likely already passed in a CollectionRoutingInfo object to the router loop.

      To prevent this use case from needing to also fetch the database information from the cache, we should allow executeCommandAgainstDatabasePrimary to be called with a CollectionRoutingInfo object, since it already contains the dbPrimary and the dbVersion.

            Assignee:
            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: