[SERVER-77914] Provide an API that indicates whether a shard can have orphans Created: 08/Jun/23  Updated: 26/Oct/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Ben Shteinfeld Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: oldshardingemea, shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-77916 Provide an API that indicates an appr... Closed
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24
Participants:
Story Points: 2

 Description   

As part of the scope for PM-2650, the query team is requesting an API from the sharding team that indicates whether a collection on a particular shard can contain orphans. This information will be used to determine whether we need to insert a shard filter stage into the query plan.



 Comments   
Comment by David Storch [ 13/Jul/23 ]

Per discussion in today's meeting with matt.panton@mongodb.com xiaochen.wu@mongodb.com jordi.serra-torrens@mongodb.com ben.shteinfeld@mongodb.com richard.hausman@mongodb.com: we should convert this into a request to add a method like ScopedCollectionFilter::allDataBelongsToMe(). That way the query system can avoid doing shard filtering if the collection is sharded but all the data is present on a single shard. If this improvement lands in time, we can implement this optimization in Bonsai as part of the project to add shard filtering to Bonsai.

Generated at Thu Feb 08 06:36:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.