[SERVER-951] Shard Key compound key Created: 09/Apr/09  Updated: 12/Jul/16  Resolved: 16/Jul/10

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

Type: Improvement Priority: Major - P3
Reporter: Eliot Horowitz (Inactive) Assignee: Mathias Stearn
Resolution: Done Votes: 9
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-943 do chunk filtering in mongod (WAS: Ma... Closed
depends on SERVER-1404 Make moveChunk in d_migrate take min/... Closed
Participants:

 Description   

might actually be done - not sure.



 Comments   
Comment by auto [ 16/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Compound key sharding test now passes SERVER-951
http://github.com/mongodb/mongo/commit/3a044ab7e9966c05fd5984b4e6438e1e38a4099e

Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Commented out compound key test SERVER-951 SERVER-1404
http://github.com/mongodb/mongo/commit/64af09f8148f92ca1ee289bc0053b6fe8c4e470b

Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Remove code to ban compound shard keys SERVER-951
http://github.com/mongodb/mongo/commit/69726e894fe3b4104fa95091910a8678bc514823

Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: compound shard keys are almost done SERVER-951
http://github.com/mongodb/mongo/commit/cfcc881427f845f7e32899839590d5a5f7021930

Comment by auto [ 14/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: ChunkMatcher compound key support SERVER-951
http://github.com/mongodb/mongo/commit/72bab0e0d279921afcdf3609fbd694ec231672ff

Comment by auto [ 13/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'redbeard0531@gmail.com'}

Message: compound key checkpoint SERVER-951
http://github.com/mongodb/mongo/commit/c460e969acda78bf3ee11d0f6c692fd2d0f50ae6

Comment by auto [ 12/Jul/10 ]

Author:

{'login': 'RedBeard0531', 'name': 'Mathias Stearn', 'email': 'mathias@10gen.com'}

Message: Chunk::countObjects() uses $min and $max SERVER-951
http://github.com/mongodb/mongo/commit/350d92f7f7e3830fde2d67db3ca1c5be7d90d3ce

Comment by Eliot Horowitz (Inactive) [ 15/Jun/10 ]

@alexander we're definitely doing it - just wanted to see at that point if it was critical or could wait (until nowish)

Comment by Alex [ 15/Jun/10 ]

Sure you could probably use subobjects for most situations but compound key sharding is almost an essential sharding feature i think and such features should not break existing applications

Comment by Michael Dirolf [ 12/Jan/10 ]

One issue might be existing datasets that are trying to add sharding.

Comment by Mathias Stearn [ 12/Jan/10 ]

Does anyone watching this have a use-case that couldn't be solved by sharding on a sub-object rather than using true compound keys?

example:

{name:

{last: "Stearn", first: "Mathias}

, ...} sharded on name
vs.

{first_name: "Mathias", last_name: "Stearn", ...}

sharded on [last_name, first_name]

Comment by Eliot Horowitz (Inactive) [ 30/Nov/09 ]

big enough change - should just push

Comment by Eliot Horowitz (Inactive) [ 28/Oct/09 ]

the trick is going to be using $min and $max for query creation

Comment by Eliot Horowitz (Inactive) [ 22/Apr/09 ]

most important compound key support.

Generated at Thu Feb 08 02:55:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.