Move memory stats from OpCtx to ClientCursor for distinct() multi-batch

XMLWordPrintableJSON

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

      Similar to how we did for SERVER-100762, we should transfer the OperationMemoryUsageTracker to the ClientCursor when a distinct() query produces more than a single batch, and write a test that shows this works.

            Assignee:
            Unassigned
            Reporter:
            Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: