[DOCS-16614] [Server] Fix advice for improving lookup performance Created: 30/Jan/24  Updated: 05/Feb/24  Resolved: 30/Jan/24

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 5.0.0, 6.0.0, 7.0.0, Server_Docs_[20240205]

Type: Task Priority: Critical - P2
Reporter: Rushan Chen Assignee: Lauren Tran
Resolution: Done Votes: 0
Labels: bug
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by DOCS-16616 [Server] Fix advice for improving loo... Closed
Problem/Incident
Participants:
Days since reply: 1 week, 1 day ago
Story Points: 2

 Description   

This ticket addresses the v5.0-v7.0 fixes. The v4.4 issue is being addressed in DOCS-16616.

4.4
https://www.mongodb.com/docs/v4.4/reference/operator/aggregation/lookup/#std-label-equality-match-performance

The text for the first row should be corrected as this:

$lookup operations that perform equality matches with a single join typically perform better when the foreign collection contains an index on the foreignField.

5.0-7.0
https://www.mongodb.com/docs/v5.0/reference/operator/aggregation/lookup/#performance-considerations
https://www.mongodb.com/docs/v6.0/reference/operator/aggregation/lookup/#performance-considerations
https://www.mongodb.com/docs/manual/reference/operator/aggregation/lookup/#performance-considerations

correct text for the first row

$lookup operations that perform equality matches with a single join typically perform better when the foreign collection contains an index on the foreignField.

remove the second bullet



 Comments   
Comment by Alison Huh [ 30/Jan/24 ]

Since this issue deals with multiple different versions of the docs, I'm going to split this up into multiple tickets to address the different version-split fixes.

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