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

Joel Bernstein commented on SOLR-4465:
--------------------------------------

Here is how custom collectors work:

There is a new "collectorFactory" element in solrconfing.xml. The design was 
deliberately kept very simple:

<collectorFactory name="default" class="solr.CollectorFactory"/>

There can be multiple collectorFactory elements defined. The "name" attribute 
is used as a handle to dynamically select a specific CollectorFactory 
implementation at query time. The "class" attribute is a subclass of 
org.apache.solr.core.CollectorFactory which defines the logic for creating the 
collector used for a specific query. The base class provides an implementation 
with default logic for choosing between the TopScoreDocCollector and 
TopFieldCollector. 

There are also new collector parameters that allow the user to select a 
collector factory by name with the following syntax:

cl.name=<name>

All parameters that begin with "cl." will be gathered up and passed to the 
CollectorFactory through the QueryCommand. These parameters can be used to 
dynamically configure collector algorithms at query time.




                
> 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
>
>
> 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]

Reply via email to