Integrate Router Role within ClusterAggregate::runAggregate

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-06-23, CAR Team 2025-07-07, CAR Team 2025-07-21, CAR Team 2025-08-04
    • None
    • 3
    • TBD
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      The goal of this ticket is to hide the complexity of the router role loop inside the implementation of ClusterAggregate::runAggregate.

      For that, runAggregate should stop receiving a CollectionRoutingInfo object as a parameter, and should instantiate a sharding::router::MultiCollectionRouter to route an aggregate command.

              Assignee:
              Silvia Surroca
              Reporter:
              Silvia Surroca
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: