Refactor ParsedUpdate to allow shapifying with unoptimized query

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • 200
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Problem

      Today, ParsedUpdate contains CanonicalQuery which has already been optimized. ParsedUpdate does not follow the common way of parsing like: raw BSON → parsed command → CmdShape → CQ. That makes shapification of updates difficult to obtain unoptimized MatchExpression for queries.

      Plan of Attack

      To make update parser acts similar to find/agg/distinct, we will separate ParsedUpdate into 2: a) real ParsedUpdate b) CanonicalUpdate. The new parsing flow looks like:

      rawBSON → ParsedUpdate → UpdateCmdShape → CanonicalUpdate

        1.
        		 Factor out parsing ParsedFindCommand and expCtx building SERVER-114317 Sub-task Closed Chi-I Huang 8.3.0-rc0

            Assignee:
            Chi-I Huang
            Reporter:
            Chi-I Huang
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: