[SERVER-2758] Consider compound indexes in shardcollection command Created: 15/Mar/11 Updated: 16/Mar/11 Resolved: 16/Mar/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 1.8.0-rc1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Janick Bernet | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When using shardcollection with a key that is a prefix of an existing compound index, one gets a message 'please create an index over the sharding key before sharding.', even though the compound index could have been used for sharding. For instance: db.Test.save( { a:1, b:2, c: 3}) ) db.runCommand({shardcollection: "test.Test", key: {a:1}}) << use compound index on a,b here instead of giving error message |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 16/Mar/11 ] |
|
See |