[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Garski updated SOLR-2592:
---------------------------------
Attachment: SOLR-2592.patch
Attached is an updated patch that includes unit tests and applies cleanly to
the latest in branch_4x. This patch corrects a bug found in unit testing where
a delete by ID may be not be forwarded to the correct shard. I created a shard
key parser implementation for testing that uses the string value of the unique
id reversed, and modified the FullSolrCloudDistribCmdsTest test to use that
implementation (which is how I found the delete by id bug). I've also added a
shard key parser with unit tests that parses the shard key value from an
underscore-delimited unique id and from a clause in a delete query. As the
shard must be parsed from the unique id for the realtime get handler a
composite id of some sort will be required for placing a document in a specific
shard.
While the solrj client is able to parse the shard key from the query and
forward it to the appropriate shard, I have not yet implemented that piece yet.
> 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: SOLR-2592.patch, dbq_fix.patch,
> 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]
