Revert "SOLR-3161 handleSelect=false by default now, and update solrconfig to not use it."

This reverts commit c53e23d2e7e1e566f30c757dbc64f40559307ecb.

git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1328821 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Dawid Weiss 2012-04-22 08:57:11 +00:00
parent afb77dd96b
commit d29d258cee
2 changed files with 23 additions and 11 deletions

View File

@ -63,7 +63,7 @@ public class SolrRequestParsers
private HashMap<String, SolrRequestParser> parsers; private HashMap<String, SolrRequestParser> parsers;
private boolean enableRemoteStreams = false; private boolean enableRemoteStreams = false;
private boolean handleSelect = false; private boolean handleSelect = true;
private StandardRequestParser standard; private StandardRequestParser standard;
/** /**

View File

@ -617,13 +617,17 @@
This section contains instructions for how the SolrDispatchFilter This section contains instructions for how the SolrDispatchFilter
should behave when processing requests for this SolrCore. should behave when processing requests for this SolrCore.
If you wish to regain use of /select?qt=... style request handler handleSelect affects the behavior of requests such as /select?qt=XXX
dispatching, then first add handleSelect="true" to
<requestDispatcher>. Then change the name of the request handler handleSelect="true" will cause the SolrDispatchFilter to process
named "/select" to something else without a leading "/", such as the request and dispatch the query to a handler specified by the
simply "select" and add default="true" to it. "qt" param
handleSelect="false" will cause the SolrDispatchFilter to
ignore "/select" requests, resulting in a 404 unless a handler
is explicitly registered with the name "/select"
--> -->
<requestDispatcher> <requestDispatcher handleSelect="true" >
<!-- Request Parsing <!-- Request Parsing
These settings indicate how Solr Requests may be parsed, and These settings indicate how Solr Requests may be parsed, and
@ -704,8 +708,16 @@
http://wiki.apache.org/solr/SolrRequestHandler http://wiki.apache.org/solr/SolrRequestHandler
Incoming requests will be dispatched to the handler with a name incoming queries will be dispatched to the correct handler
equal to the remainder of the URL path, starting with a '/'. based on the path or the qt (query type) param.
Names starting with a '/' are accessed with the a path equal to
the registered name. Names without a leading '/' are accessed
with: http://host/app/[core/]select?qt=name
If a /select request is processed with out a qt param
specified, the requestHandler that declares default="true" will
be used.
If a Request Handler is declared with startup="lazy", then it will If a Request Handler is declared with startup="lazy", then it will
not be initialized until the first request that uses it. not be initialized until the first request that uses it.
@ -720,7 +732,7 @@
of SearchComponents (see below) and supports distributed of SearchComponents (see below) and supports distributed
queries across multiple shards queries across multiple shards
--> -->
<requestHandler name="/select" class="solr.SearchHandler"> <requestHandler name="search" class="solr.SearchHandler" default="true">
<!-- default values for query parameters can be specified, these <!-- default values for query parameters can be specified, these
will be overridden by parameters in the request will be overridden by parameters in the request
--> -->
@ -1252,7 +1264,7 @@
In reality you will likely want to add the component to your In reality you will likely want to add the component to your
already specified request handlers. already specified request handlers.
--> -->
<requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy"> <requestHandler name="tvrh" class="solr.SearchHandler" startup="lazy">
<lst name="defaults"> <lst name="defaults">
<bool name="tv">true</bool> <bool name="tv">true</bool>
</lst> </lst>