lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Laird (JIRA)" <>
Subject [jira] [Commented] (SOLR-2592) Pluggable shard lookup mechanism for SolrCloud
Date Tue, 31 Jul 2012 18:34:35 GMT


Andy Laird commented on SOLR-2592:

Requiring that the document never move to a different slice is certainly ideal but a very
important use case involves field collapsing.  The only way to make the counts work for field-collapsed
results in a multi-shard setup is to ensure that docs with the same to-be-collapsed value
reside on the same slice.  If that field changes we may have to move the document, I don't
see any way around that (unless someone can make field collapse counts work in distributed
setups).  Does ElasticSearch handle field-collapse for multi-shards?

> 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: SOLR-2592.patch, SOLR-2592_rev_2.patch, dbq_fix.patch, pluggable_sharding.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:!default.jspa
For more information on JIRA, see:


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

View raw message