[
https://issues.apache.org/jira/browse/SOLR-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587519#comment-13587519
]
Joel Bernstein commented on SOLR-4465:
--------------------------------------
Sure.
One use case would be to control distribution of document types within a result
set. For example if you wanted to ensure that each page had 10% of content type
A and 50% of type B and 40% of type C.
You could insert a custom collector that would manage this. The mergeIds()
method would becomes part of the collectorFactory so that the algorithm used at
the shard level could be maintained over distributed search.
> Configurable Collectors
> -----------------------
>
> Key: SOLR-4465
> URL: https://issues.apache.org/jira/browse/SOLR-4465
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 4.1
> Reporter: Joel Bernstein
> Fix For: 4.2, 5.0
>
> Attachments: SOLR-4465.patch, SOLR-4465.patch, SOLR-4465.patch,
> SOLR-4465.patch, SOLR-4465.patch, SOLR-4465.patch, SOLR-4465.patch,
> SOLR-4465.patch
>
>
> This issue is to add configurable custom collectors to Solr. This expands the
> design and work done in issue SOLR-1680 to include:
> 1) CollectorFactory configuration in solconfig.xml
> 2) Http parameters to allow clients to dynamically select a CollectorFactory
> and construct a custom Collector.
> 3) Make aspects of QueryComponent pluggable so that the output from
> distributed search can conform with custom collectors at the shard level.
--
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: [email protected]
For additional commands, e-mail: [email protected]
