Reduce danger of MatchExpression::getChildVector() or remove it

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: Internal Code, Querying
    • None
    • Fully Compatible
    • Query 2019-12-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As detailed in SERVER-45177, this API is dangerous to use and overlaps in functionality with MatchExpression::getChild(size_t). We should investigate why this method was added and whether we should audit all implementations to make sure they don't return nullptr like MatchExpressionNot, or we should remove it and replace usages with getChild()

              Assignee:
              Jacob Evans (Inactive)
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: