Investigate why an aggregation running in config server is not able to target other shards

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When running an aggregation in the config server, the mongo process interface is implemented as a NonShardSvrProcessInterface (LINK), not being able to target other shards. Does it make sense, in order to target other shards, it could implement ShardServerProcessInterface?. The problem is that, while executing aggregation stages in the config server, ShardingState::get(opCtx)->enabled() is set false.

      It exists the possibility it is coded with this intention.

            Assignee:
            [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            Pol Castuera (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: