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

Investigate what other StageConstraints are "inheritable"

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Aggregation Framework
    • Query

    Description

      In SERVER-35419, we're introducing a new helper that iterates over a pipeline of DocumentSources and "resolves" the strictest DiskUseRequirement and TransactionRequirement. This code is helpful for the $lookup and $facet stages, which have sub-pipelines of their own and "inherit" the strictest requirement of their children.

      This ticket is to investigate what other StageConstraints should be inherited, if any. If there are more, we can genericize StageConstraints::resolveDiskUseAndTransactionRequirement()
      to resolve all such constraints. charlie.swanson thinks that FacetRequirement might be eligible. ChangeStreamRequirement looks like it could be eligible, but the existence of kChangeStreamStage makes it seem difficult.

      Attachments

        Activity

          People

            backlog-server-query Backlog - Query Team (Inactive)
            kyle.suarez@mongodb.com Kyle Suarez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: