[
https://issues.apache.org/jira/browse/SOLR-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426000#comment-13426000
]
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: 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: SOLR-2592.patch, SOLR-2592_rev_2.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]
