[DOCS-15641] Investigate changes in SERVER-69748: "pipelineUsesLookup" field is tracked incorrectly in CurOp Created: 21/Sep/22  Updated: 13/Nov/23  Resolved: 21/Oct/22

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: 6.2.0-rc0
Fix Version/s: 6.2.0-rc0, 6.1.1, 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: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-69748 "pipelineUsesLookup" field is tracked... Closed
Participants:
Days since reply: 1 year, 15 weeks, 5 days ago
Epic Link: DOCSP-21764

 Description   
Original Downstream Change Summary

Removed a recently added field from serverStatus

Description of Linked Ticket

Currently, we only set the field to true for the initial section of the pipeline, not after any pipelines that cannot be pushed down. For the following pipeline:

[{$graphLookup: ...}, {$lookup: }]

Since $groupLookup is not pushed down, the second $lookup will not be counted.

https://github.com/10gen/mongo/blob/830439daf3e0ce06af04c8fa84b53f7b9aa3d759/src/mongo/db/pipeline/pipeline_d.cpp#L188



 Comments   
Comment by Sarah Olson [ 21/Oct/22 ]

No significant user impact.

Comment by Education Bot [ 06/Oct/22 ]

Fix Version updated for upstream SERVER-69748:
6.2.0-rc0, 6.1.1

Comment by Education Bot [ 05/Oct/22 ]

Fix Version updated for upstream SERVER-69748:
6.2.0-rc0, 6.1.0-rc5

Comment by Education Bot [ 21/Sep/22 ]

Fix Version updated for upstream SERVER-69748:
6.2.0-rc0

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