lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Garski (JIRA)" <>
Subject [jira] [Commented] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud
Date Sun, 16 Sep 2012 14:42:07 GMT


Michael Garski commented on SOLR-2592:

Thanks for the feedback Noble! I will update the patch I submitted with the following:

* Add the definition of a shardKey field in the schema, similar to how the unique id is defined.
If no shardKey field is defined in the schema, the value hashed will fall back to the unique
* Add support for an optional shard.key.val request parameter to the realtime get handler,
if the value is not specified the query will be distributed.
* Add support for an optional property on the delete command for shard.key.val, if the value
is not specified the delete will be distributed.
* Remove the pluggable implementation on how the value to be hashed is determined.
> Pluggable shard lookup mechanism for SolrCloud
> ----------------------------------------------
>                 Key: SOLR-2592
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrCloud
>    Affects Versions: 4.0-ALPHA
>            Reporter: Noble Paul
>            Assignee: Mark Miller
>         Attachments: dbq_fix.patch, pluggable_sharding.patch, pluggable_sharding_V2.patch,
SOLR-2592.patch, SOLR-2592_r1373086.patch, SOLR-2592_r1384367.patch, SOLR-2592_rev_2.patch,
> If the data in a cloud can be partitioned on some criteria (say range, hash, attribute
value etc) It will be easy to narrow down the search to a smaller subset of shards and in
effect can achieve more efficient search.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message