[COMPASS-6152] Investigate changes in SERVER-69748: "pipelineUsesLookup" field is tracked incorrectly in CurOp Created: 21/Sep/22  Updated: 22/Sep/22  Resolved: 22/Sep/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-69748 "pipelineUsesLookup" field is tracked... Closed
Documentation Changes: Not Needed

 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 Anna Henningsen [ 22/Sep/22 ]

No impact.

Generated at Wed Feb 07 22:42:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.