[
https://issues.apache.org/jira/browse/SOLR-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734284#action_12734284
]
Hoss Man commented on SOLR-1237:
--------------------------------
i think we make QuerySenderListener pass in a special param (init=newSearcher
or init=firstSearcher), and i think we document that param, and i think we let
people who implement their own SolrEventListeners worry about sending that
param themselves if they want/need to...
If we do it right, we can leave it so people can explicitly override the param
in the solrconfig.xml (ie: init=none) so people can hide the fact that it's a
warming query if they really, really, want to.
> firstSearcher and newSearcher should identify themselves via the parameter
> set passed in
> ----------------------------------------------------------------------------------------
>
> Key: SOLR-1237
> URL: https://issues.apache.org/jira/browse/SOLR-1237
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.4
>
>
> The firstSearcher and newSearcher events call the regular search component
> chain, but are special cases. They should identify themselves by passing in
> a parameter indicating their type. This way, for instance, the sharding
> component could know to ignore the &shards parameter, which currently causes
> Solr to hang if it is present in the firstSearcher query string.
> See
> http://www.lucidimagination.com/search/document/b2b9c39a8eb4e563/firstsearcher_and_newsearcher_events
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
