[SERVER-2949] sharding server should have multiple shard keys support Created: 14/Apr/11  Updated: 29/Aug/11  Resolved: 14/Apr/11

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 1.8.1
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: davyzhang Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

I use
db.runCommand( { shardcollection : "test.users" , key : {_id:1, email : 1 ,address:1}
to shard

but only _id can be used to route queries, query only on email and address can not be targeted the server search all the mongod processes.
so I think is there any possibility to specify more shard keys not used to shard but work as "global indexes", used to route queries
this will increase the shard performance greatly



 Comments   
Comment by Eliot Horowitz (Inactive) [ 14/Apr/11 ]

This would require keeping a global index for the secondary shard keys since the ranges are totally different.
This would be incredibly costly, and is not practical.

Generated at Thu Feb 08 03:01:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.