On Fri, Jan 25, 2013 at 3:59 PM, davers <[email protected]> wrote:
> I want to shard on groupid instead of id but it doesn't seem to be working.
That's not yet implemented.
Currently you need to put the group in the ID. From the release notes:
* Simple multi-tenancy through enhanced document routing:
- The "compositeId" router is the default for collections with hash
based routing (i.e. when numShards=N is specified on collection
creation).
- Documents with ids sharing the same domain/prefix, e.g.
'customerB!', will be routed to the same shard, allowing for
efficient querying. At query time, one can specify a "shard.keys"
parameter that lists the domains, e.g. 'shard.keys=customerB!', and
controls what shards the query is routed to.
- Collections that do not specify numShards at collection creation
time use custom sharding and default to the "implicit" router.
Document updates received by a shard will be indexed to that shard,
unless a "_shard_" parameter or document field names a different
shard.
-Yonik
http://lucidworks.com
