[DOCS-13259] Investigate changes in SERVER-21784: Track 'nReturned' and 'executionTimeMillis' execution stats for each aggregation pipeline stage and expose via explain Created: 02/Dec/19  Updated: 13/Nov/23  Resolved: 16/Jun/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.3, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kanchana Sekhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-21784 Track 'nReturned' and 'executionTimeM... Closed
Participants:
Days since reply: 3 years, 34 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

When running aggregate explain with verbosities "executionStats" and "allPlansExecution", the output will include "nReturned" and "executionTimeMillisEstimate" for each aggregation stage.

Description of Linked Ticket

For the same reason explain exists for .find(), it would be helpful to know how long an aggregation pipeline takes to run and within each stage. In many ways it is even more important with .aggregate() because of potentially multiple pipeline expressions for the same result.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Kanchana Sekhar [ 16/Jun/20 ]

Merged PR

Comment by Githook User [ 16/Jun/20 ]

Author:

{'name': 'Kanchana Sekhar', 'email': 'kanchana.sekhar@mongodb.com', 'username': 'kanchana-mongodb'}

Message: DOCS-13259 doc updates to RN for expand field support
Branch: master
https://github.com/mongodb/docs/commit/0e65fa263aad85eea081ca40f4488ce0658a858f

Generated at Thu Feb 08 08:07:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.