lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Rosher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud
Date Thu, 13 Sep 2012 09:13:09 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454757#comment-13454757
] 

Dan Rosher commented on SOLR-2592:
----------------------------------

Hi,

We also have a use case where we need to divvy the index into specific slices such that a
document ends up on a specific slice, in a way that all docs on that slice are related, in
effect a filter of the collection of docs.

Unfortunately this patch didn't meet our needs, so I've written one (SOLR_2592_solr_4_0_0_BETA_ShardPartitioner
)that allows a user to create a ShardPartitioner to be more flexible about which shard a document
might live. ShardPartitioner is pluggable and added via solrconfig.xml.

The default is a HashShardPartitioner that works much like the existing implementation, and
as an example I've also added a NamedShardPartitioner. This might be used to partition by
date for example, or any other field value.

It's against 4.0 Beta since that's what we're using, and meant changing some of the core testing
src to test NamedShardPartitioner. 

Perhaps someone might be able to take a look and comment?

Cheers,
Dan
                
> 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-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_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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message