Add optimizer metrics to curOp

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • QO 2023-11-13, QO 2023-11-27, QO 2023-12-11, QO 2023-12-25
    • 165
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Class curOp contains data specific for the operation and will add estimatedCost, estimatedCardinality, and the query key (as it is defined in the map - see references). curOp already contains information about whether the plan used a collection scan, as well as executionTime and optimizationTime. This will satisfy the goals form the scope to add the data for the system.profile and explain output.

            Assignee:
            Misha Tyulenev (Inactive)
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: