[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13284187#comment-13284187
]
Michael Garski commented on SOLR-2592:
--------------------------------------
The pluggable_sharding_V2.patch does work with the latest version of trunk,
however I would recommend running the unit tests after applying the patch to
verify things on your end. I am hesitant to recommend the patch for production
use as it does change the value that is hashed from the indexed value to the
string value of the unique id which changes the behavior of the current hashing
if your unique id is a numeric field type.
I am using the patch with the latest from a few days ago for testing and am
using composite unique ids (123_456_789) so I created a ShardKeyParser that
hashes on the first id in the composite (123) and parses a clause out of a
delete by query to route updates and deletes to the appropriate shards. In
order to direct the query to a particular shard use the shard.keys param set to
the value that should be hashed (123).
> Pluggable shard lookup mechanism for SolrCloud
> ----------------------------------------------
>
> Key: SOLR-2592
> URL: https://issues.apache.org/jira/browse/SOLR-2592
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.0
> Reporter: Noble Paul
> Attachments: pluggable_sharding.patch, pluggable_sharding_V2.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
