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

Separate ExpressionContext into ExpressionContext and AggregationContext

    • Query Optimization
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      Due to the introduction of Expression into MatchExpression, we now use the ExpressionContext inside of MatchExpression. But ExpressionContext has members such as AggregationRequest parameters and an owned CollatorInterface that do not make sense outside of aggregation. We would like ExpressionContext to only contain members relevant to Expression (opCtx, variables, variablesParseState, and _collator) and make a new AggregationContext to hold an ExpressionContext and all the other state relevant to aggregation. AggregationContext will be used inside of aggregation, and an Expression should only hold an ExpressionContext, which makes sense to use outside of aggregation.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: