refactor the document scan fn to use functions from the public api

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2026-06-22, QE 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Comment from mickey.winters@mongodb.com:
      I think instead of calling ClusterAggregate::runAggregate() and the other runAggregate directly (which aren't part of the public API), we should try using something that is in the public API. if we use CommandHelpers::runCommandDirectly then the aggregate will run as if we sent a command to the mongod directly. IIUC we should be able to call that with {"clusterAggregate": ..., pipeline: [...], ...} for sharded clusters and {"aggregate": ..., pipeline: [...], ...}. then you can just pass a bool as a parameter to noDocumentsViolatingValidator.

            Assignee:
            Mickey Winters
            Reporter:
            Kristina Znam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: