[SERVER-924] use same shard key and chunks config on multiple collections Created: 13/Oct/09 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 9 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Comments |
| Comment by Nic Cottrell [ 23/Mar/20 ] |
|
What's the use case for this? A multi-tenant setup where many databases have the same repeated collections? Or for multiple collections in the same database that happen to use the same fields? |
| Comment by Nathaniel Cook [ 07/Sep/13 ] |
|
A team of four of us have some time to dedicate to a first implementation of this feature. We have some ideas of our own but if any voters, watchers, or others have any recommendations they would be much appreciated. Thanks. |