[SERVER-5133] all collections accessed via mongos should be considered sharded Created: 28/Feb/12 Updated: 15/Feb/13 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
"unsharded" collections should be a special case where a collection exists only on a single shard and is implicitly sharded by _id (or potentially a special empty-key value). This simplifies much of the sharding logic and eliminates much complexity handling changes between sharded and unsharded collection state. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Sep/12 ] |
|
calling this a dup of SERVER-939, since implementing this gets that. |