[SERVER-58300] Generalize the concept of a shard-local collection Created: 06/Jul/21  Updated: 26/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Hana Pearlman Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: PM-2144-Milestone-0, oldshardingemea
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-58220 Sharded $lookup attempts to run shard... Closed
Assigned Teams:
Catalog and Routing
Sprint: Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
Participants:

 Description   

In SERVER-58220, we considered creating a new method NamespaceString::isShardLocalNamespace() to determine whether or not a namespace exists locally and independently on each shard. The work was put off for a more targeted approach.

This ticket is to track a broader approach. We should consider generalizing the concept of a shard-local collection. This work should be coordinated with Sharding EMEA to ensure representations in the code are consistent.


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