Correctly track _isIncompatibleWithMemoryTracking from foreign coll in $lookup

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      A similar case to https://jira.mongodb.org/browse/SERVER-104719 can also appear with _isIncompatibleWithMemoryTracking, since the flag is not cloned in ExpressionContext::copyWith(). This could cause problems if we have an exchange (which shouldn't track memory) that has a subpipeline and _isIncompatibleWithMemoryTracking=true is not copied over into the subpipeline.

            Assignee:
            Unassigned
            Reporter:
            Erin Liang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: