Make DB/Collection/MultiCollectionRouter's constructors take OperationContext

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-12-08
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The DBPrimary, Collection and MultiCollection Routers are all expected to run on the same operation context and as such it does not change. It would be much cleaner if the OpContext was set once at construction time and then their methods don't take OpContext at all.

      This also allows us to better implement tracking for the purposes of disallowing nesting (SERVER-114458).

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: