[DOCS-10778] Limitations of aggregations in sharding Created: 12/Sep/17  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Torsten Spindler Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: docs-triage, sharding-docs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-10817 Missed reference to $graphlookup in a... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Is there a single page mentioning the limitations of sharding and aggregation? I was pointed to $lookup and $graphLookup which both state that the $from collection cannot be sharded. Maybe that deserves a page of it’s own or be added to https://docs.mongodb.com/manual/core/sharded-cluster-requirements/



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Torsten Spindler [ 14/Sep/17 ]

Further comments from the slack discussion:

Another thing to keep in mind is that you can't do covered queries, fast counts (COUNT_SCAN), fast distinct (DISTINCT_SCAN) sharded unless you use a secondary read preference

And if you do use a secondary read preference then all of those things give wrong answers

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