[jira] Updated: (SOLR-1237) firstSearcher and newSearcher should identify themselves via the parameter set passed in

["Grant Ingersoll (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Ingersoll updated SOLR-1237:
----------------------------------

    Attachment: SOLR-1237.patch

Fixed the names.  Plan on committing in a day or two.

> 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
>
>         Attachments: SOLR-1237.patch, SOLR-1237.patch
>
>
> 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.