You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Scott Hollenbeck <sa...@musclecarresearch.com.INVALID> on 2015/08/27 21:10:18 UTC
"no default request handler is registered"
I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of
the Apache Solr Search module for Drupal. Things seem to be working fine,
except that this warning message appears in the Solr admin logging window
and in the server log:
"no default request handler is registered (either '/select' or 'standard')"
Looking at the solrconfig.xml file that comes with the Drupal module I see a
requestHandler named "standard":
<requestHandler name="standard" class="solr.SearchHandler">
<lst name="defaults">
<str name="df">content</str>
<str name="echoParams">explicit</str>
<bool name="omitHeader">true</bool>
</lst>
</requestHandler>
I also see a handler named pinkPony with a "default" attribute set to
"true":
<!-- trivia: the name pinkPony requestHandler was an agreement between the
Search API and the
apachesolr maintainers. The decision was taken during the Drupalcon
Munich codesprint.
-->
<requestHandler name="pinkPony" class="solr.SearchHandler" default="true">
<lst name="defaults">
<str name="defType">edismax</str>
<str name="df">content</str>
<str name="echoParams">explicit</str>
<bool name="omitHeader">true</bool>
<float name="tie">0.01</float>
<!-- Don't abort searches for the pinkPony request handler (set in
solrcore.properties) -->
<int name="timeAllowed">${solr.pinkPony.timeAllowed:-1}</int>
<str name="q.alt">*:*</str>
<!-- By default, don't spell check -->
<str name="spellcheck">false</str>
<!-- Defaults for the spell checker when used -->
<str name="spellcheck.onlyMorePopular">true</str>
<str name="spellcheck.extendedResults">false</str>
<!-- The number of suggestions to return -->
<str name="spellcheck.count">1</str>
</lst>
<arr name="last-components">
<str>spellcheck</str>
<str>elevator</str>
</arr>
</requestHandler>
So it seems like there are both standard and default requestHandlers
specified. Why is the warning produced? What am I missing?
Thank you,
Scott
Re: "no default request handler is registered"
Posted by Chris Hostetter <ho...@fucit.org>.
I just want to clarify: all of Shawn's points below are valid and good --
but they stll don't explain the warning messgae you are getting. it makes
no sense as the code is currently written, and doesn't do anything to help
encourage people to transition to path based handler names.
: Date: Thu, 27 Aug 2015 13:50:51 -0600
: From: Shawn Heisey <ap...@elyograg.org>
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: "no default request handler is registered"
:
: On 8/27/2015 1:10 PM, Scott Hollenbeck wrote:
: > I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of
: > the Apache Solr Search module for Drupal. Things seem to be working fine,
: > except that this warning message appears in the Solr admin logging window
: > and in the server log:
: >
: > "no default request handler is registered (either '/select' or 'standard')"
: >
: > Looking at the solrconfig.xml file that comes with the Drupal module I see a
: > requestHandler named "standard":
: >
: > <requestHandler name="standard" class="solr.SearchHandler">
: > <lst name="defaults">
: > <str name="df">content</str>
: > <str name="echoParams">explicit</str>
: > <bool name="omitHeader">true</bool>
: > </lst>
: > </requestHandler>
: >
: > I also see a handler named pinkPony with a "default" attribute set to
: > "true":
:
: <snip>
:
: > So it seems like there are both standard and default requestHandlers
: > specified. Why is the warning produced? What am I missing?
:
: I think the warning message may be misworded, or logged in incorrect
: circumstances, and might need some attention.
:
: The solrconfig.xml that you are using (which I assume came from the
: Drupal project) is geared towards a 3.x version of Solr prior to 3.6.x
: (the last minor version in the 3.x line).
:
: Starting in the 3.6 version, all request handlers in examples have names
: that start with a forward slash, like "/select", none of them have the
: "default" attribute, and the handleSelect parameter found elsewhere in
: the solrconfig.xml is false.
:
: You should bring this up with the Drupal folks and ask them to upgrade
: their config/schema and their code for modern versions of Solr. Solr
: 3.6.0 (which deprecated their handler naming convention and the
: "default" attribute) was released over three years ago.
:
: More info than you probably wanted to know: The reason this change was
: made is security-related. With the old way of naming request handlers
: and handling /select indirectly, you could send a query to /select,
: include a qt=/update parameter, and change the index via a handler
: intended only for queries.
:
: Thanks,
: Shawn
:
:
-Hoss
http://www.lucidworks.com/
RE: "no default request handler is registered"
Posted by Scott Hollenbeck <sa...@musclecarresearch.com.INVALID>.
> -----Original Message-----
> From: Shawn Heisey [mailto:apache@elyograg.org]
> Sent: Thursday, August 27, 2015 3:51 PM
> To: solr-user@lucene.apache.org
> Subject: Re: "no default request handler is registered"
>
> On 8/27/2015 1:10 PM, Scott Hollenbeck wrote:
> > I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of
> > the Apache Solr Search module for Drupal. Things seem to be working fine,
> > except that this warning message appears in the Solr admin logging window
> > and in the server log:
> >
> > "no default request handler is registered (either '/select' or 'standard')"
> >
> > Looking at the solrconfig.xml file that comes with the Drupal module I see a
> > requestHandler named "standard":
> >
> > <requestHandler name="standard" class="solr.SearchHandler">
> > <lst name="defaults">
> > <str name="df">content</str>
> > <str name="echoParams">explicit</str>
> > <bool name="omitHeader">true</bool>
> > </lst>
> > </requestHandler>
> >
> > I also see a handler named pinkPony with a "default" attribute set to
> > "true":
>
> <snip>
>
> > So it seems like there are both standard and default requestHandlers
> > specified. Why is the warning produced? What am I missing?
>
> I think the warning message may be misworded, or logged in incorrect
> circumstances, and might need some attention.
>
> The solrconfig.xml that you are using (which I assume came from the
> Drupal project) is geared towards a 3.x version of Solr prior to 3.6.x
> (the last minor version in the 3.x line).
>
> Starting in the 3.6 version, all request handlers in examples have names
> that start with a forward slash, like "/select", none of them have the
> "default" attribute, and the handleSelect parameter found elsewhere in
> the solrconfig.xml is false.
>
> You should bring this up with the Drupal folks and ask them to upgrade
> their config/schema and their code for modern versions of Solr. Solr
> 3.6.0 (which deprecated their handler naming convention and the
> "default" attribute) was released over three years ago.
Thanks for the replies. The config files I'm using came from a Drupal sandbox project that's focused on Solr 5.x compatibility. I've added an issue to that project's queue. We'll see how it goes.
Scott Hollenbeck
Re: "no default request handler is registered"
Posted by Shawn Heisey <ap...@elyograg.org>.
On 8/27/2015 1:10 PM, Scott Hollenbeck wrote:
> I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of
> the Apache Solr Search module for Drupal. Things seem to be working fine,
> except that this warning message appears in the Solr admin logging window
> and in the server log:
>
> "no default request handler is registered (either '/select' or 'standard')"
>
> Looking at the solrconfig.xml file that comes with the Drupal module I see a
> requestHandler named "standard":
>
> <requestHandler name="standard" class="solr.SearchHandler">
> <lst name="defaults">
> <str name="df">content</str>
> <str name="echoParams">explicit</str>
> <bool name="omitHeader">true</bool>
> </lst>
> </requestHandler>
>
> I also see a handler named pinkPony with a "default" attribute set to
> "true":
<snip>
> So it seems like there are both standard and default requestHandlers
> specified. Why is the warning produced? What am I missing?
I think the warning message may be misworded, or logged in incorrect
circumstances, and might need some attention.
The solrconfig.xml that you are using (which I assume came from the
Drupal project) is geared towards a 3.x version of Solr prior to 3.6.x
(the last minor version in the 3.x line).
Starting in the 3.6 version, all request handlers in examples have names
that start with a forward slash, like "/select", none of them have the
"default" attribute, and the handleSelect parameter found elsewhere in
the solrconfig.xml is false.
You should bring this up with the Drupal folks and ask them to upgrade
their config/schema and their code for modern versions of Solr. Solr
3.6.0 (which deprecated their handler naming convention and the
"default" attribute) was released over three years ago.
More info than you probably wanted to know: The reason this change was
made is security-related. With the old way of naming request handlers
and handling /select indirectly, you could send a query to /select,
include a qt=/update parameter, and change the index via a handler
intended only for queries.
Thanks,
Shawn
Re: "no default request handler is registered"
Posted by Chris Hostetter <ho...@fucit.org>.
Thats... strange.
Looking at hte code it appears to be a totally bogus and missleading
warning -- but it also shouldn't affect anything.
You can feel free to ignore it for now...
https://issues.apache.org/jira/browse/SOLR-7984
: Date: Thu, 27 Aug 2015 15:10:18 -0400
: From: Scott Hollenbeck <sa...@musclecarresearch.com.invalid>
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: "no default request handler is registered"
:
: I'm doing some experimenting with Solr 5.3 and the 7.x-1.x-dev version of
: the Apache Solr Search module for Drupal. Things seem to be working fine,
: except that this warning message appears in the Solr admin logging window
: and in the server log:
:
: "no default request handler is registered (either '/select' or 'standard')"
:
: Looking at the solrconfig.xml file that comes with the Drupal module I see a
: requestHandler named "standard":
:
: <requestHandler name="standard" class="solr.SearchHandler">
: <lst name="defaults">
: <str name="df">content</str>
: <str name="echoParams">explicit</str>
: <bool name="omitHeader">true</bool>
: </lst>
: </requestHandler>
:
: I also see a handler named pinkPony with a "default" attribute set to
: "true":
:
: <!-- trivia: the name pinkPony requestHandler was an agreement between the
: Search API and the
: apachesolr maintainers. The decision was taken during the Drupalcon
: Munich codesprint.
: -->
: <requestHandler name="pinkPony" class="solr.SearchHandler" default="true">
: <lst name="defaults">
: <str name="defType">edismax</str>
: <str name="df">content</str>
: <str name="echoParams">explicit</str>
: <bool name="omitHeader">true</bool>
: <float name="tie">0.01</float>
: <!-- Don't abort searches for the pinkPony request handler (set in
: solrcore.properties) -->
: <int name="timeAllowed">${solr.pinkPony.timeAllowed:-1}</int>
: <str name="q.alt">*:*</str>
:
: <!-- By default, don't spell check -->
: <str name="spellcheck">false</str>
: <!-- Defaults for the spell checker when used -->
: <str name="spellcheck.onlyMorePopular">true</str>
: <str name="spellcheck.extendedResults">false</str>
: <!-- The number of suggestions to return -->
: <str name="spellcheck.count">1</str>
: </lst>
: <arr name="last-components">
: <str>spellcheck</str>
: <str>elevator</str>
: </arr>
: </requestHandler>
:
: So it seems like there are both standard and default requestHandlers
: specified. Why is the warning produced? What am I missing?
:
: Thank you,
: Scott
:
:
-Hoss
http://www.lucidworks.com/