[SERVER-69748] "pipelineUsesLookup" field is tracked incorrectly in CurOp Created: 15/Sep/22 Updated: 29/Oct/23 Resolved: 21/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.1, 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rui Liu | Assignee: | Jennifer Peshansky (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v6.1
|
||||||||||||||||||||
| Sprint: | QE 2022-10-03 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 05/Oct/22 ] |
|
Author: {'name': 'Jennifer Peshansky', 'email': 'jennifer.peshansky@mongodb.com', 'username': 'jenniferpeshansky'}Message: (cherry picked from commit 6f450a3cea6287612329f44e90536d72fe7c16c5) |
| Comment by Githook User [ 21/Sep/22 ] |
|
Author: {'name': 'Jennifer Peshansky', 'email': 'jennifer.peshansky@mongodb.com', 'username': 'jenniferpeshansky'}Message: |
| Comment by Jennifer Peshansky (Inactive) [ 20/Sep/22 ] |
|
This field is redundant since we already have a generic way of counting the usage of any operator. We can probably remove it. For reference, it was added as part of |