[SERVER-4773] Could shardcollection implicity enablesharding on the database? Created: 25/Jan/12 Updated: 14/Oct/23 Resolved: 14/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Tommaso Tocci |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | RachitaD, pm-1051-legacy-tickets | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding NYC
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Why doesn't shardcollection imply enablesharding on the db? |
| Comments |
| Comment by Asya Kamsky [ 13/Sep/17 ] |
|
If the database doesn't already exist, enableSharding could optionally take a parameter specifying which shard should be the primary shard for it. |
| Comment by Greg Studer [ 03/Apr/13 ] |
|
Related to SERVER-939 in that enableSharding was initially meant for that purpose, but will probably be deprecated for a new parameter. |
| Comment by Eliot Horowitz (Inactive) [ 02/Apr/13 ] |
|
This is being considered as part of something else. |
| Comment by Richard Kreuter (Inactive) [ 26/Jan/12 ] |
|
By way of background, this question comes up a lot in trainings, and I've never been able to think up a reason why it couldn't. |