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

David Smiley updated SOLR-6807:
-------------------------------
    Attachment: SOLR_6807_handleSelect_false.patch

Attached is my work in progress.  SolrJ & Contrib tests pass (which took a bit 
of work).  I'm working through -core now.

* change SolrConfig handleSelect read default now based on luceneMatchVersion
* changed all solrconfigs to remove all reference to handleSelect & qt
* changed all solrconfigs such that <requestHandler /select 
class="SearchHandler"/> is registered. I found many old test configs 
referencing name="standard" and class StandardRequestHandler and sometimes with 
a superfluous default="true".
* SolrTestCaseJ4 had some utility methods referencing the "standard" request 
handler that I replaced with "".. The empty string is a special value which 
results in choosing the default one which will be either /select or standard 
depending on which is registered.

Since this isn't a "feature" or strictly an "improvement" but just a change of 
defaults / housekeeping, I think this can go to 7.0?

> Make handleSelect=false by default
> ----------------------------------
>
>                 Key: SOLR-6807
>                 URL: https://issues.apache.org/jira/browse/SOLR-6807
>             Project: Solr
>          Issue Type: Wish
>    Affects Versions: 4.10.2
>            Reporter: Alexandre Rafalovitch
>            Assignee: David Smiley
>            Priority: Minor
>              Labels: solrconfig.xml
>             Fix For: 5.0
>
>         Attachments: SOLR_6807_handleSelect_false.patch
>
>
> In the solrconfig.xml, we have a long explanation on the legacy 
> *<requestDispatcher handleSelect="false" >* section. Since we are cleaning up 
> legacy stuff for version 5, is it safe now to flip handleSelect's default to 
> be *false* and therefore remove both the attribute and the whole section 
> explaining it?
> Then, a section in Reference Guide or even a blog post can explain what to do 
> for the old clients that still need it. But it does not seem to be needed 
> anymore for the new users. And possibly cause confusing now that we have 
> implicit, explicit and overlay handlers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to