[
https://issues.apache.org/jira/browse/SOLR-14382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074771#comment-17074771
]
Christine Poerschke commented on SOLR-14382:
--------------------------------------------
We have a use case for two distinct {{QueryComponent}} customisations for field
vs. score sorted searches.
This could be supported via two different search handlers e.g.
{code}
<searchComponent name="queryFoo" class="com.company.team.FooQueryComponent"/>
<requestHandler name="/selectFoo" class="solr.SearchHandler">
<arr name="components">
...
<str>queryFoo</str>
...
</arr>
...
</requestHandler>
<searchComponent name="queryBar" class="com.company.team.BarQueryComponent"/>
<requestHandler name="/selectBar" class="solr.SearchHandler">
<arr name="components">
...
<str>queryBar</str>
...
</arr>
...
</requestHandler>
{code}
but this would introduce complexity on the client side i.e. the client needs to
send to different end-points depending on the type of search.
As an alternative to this we think a custom 'query component multiplexer' could
work e.g.
{code}
<searchComponent name="query"
class="com.company.team.QueryComponentMultiplexer"/>
{code}
replaces the default {{org.apache.solr.handler.component.QueryComponent}} and
switches behaviour depending on the search parameters.
> delegating search component
> ---------------------------
>
> Key: SOLR-14382
> URL: https://issues.apache.org/jira/browse/SOLR-14382
> Project: Solr
> Issue Type: New Feature
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
>
> (details to follow)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
