lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Bernstein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4465) Configurable Collectors
Date Mon, 04 Mar 2013 20:05:13 GMT

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

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

Dan,

This patch doesn't work with grouping because grouping is done within a separate flow with
a separate set of collectors. SOLR-1680 was a custom collectors patch that was meant to allow
grouping to be merged into the main flow, but was never committed. Possibly grouping could
be implemented using a collector factory but that would be a follow-on to getting this as
part of the core.

I'll work on resolving the npe with the default collector in the next patch.

As you mentioned the caching implications here need to be fully understood. Perhaps you could
elaborate on "Additionally since the collector is free to alter results between requests".
Can you explain the use case where this would occur?


                
> 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, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message