lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norberto Meijome <>
Subject Re: SpellCheckerRequestHandler & qt parameter
Date Fri, 27 Jun 2008 01:41:48 GMT
On Thu, 26 Jun 2008 16:25:46 -0500 (CDT)
"Geoffrey Young" <> wrote:

> well *almost* - it works most excellently with q=$term but when I add
> spellchecker.q=$term things implode:
> HTTP Status 500 - null java.lang.NullPointerException at
> org.apache.solr.handler.component.SpellCheckComponent.getTokens(
> org.apache.solr.handler.component.SpellCheckComponent.process(
> org.apache.solr.handler.component.SearchHandler.handleRequestBody(
> org.apache.solr.handler.RequestHandlerBase.handleRequest(
at org.apache.solr.core.SolrCore.execute( at
> org.apache.solr.servlet.SolrDispatchFilter.execute( at
> org.apache.solr.servlet.SolrDispatchFilter.doFilter( at...
> not being a java guy I need to use solr out of the box, and adding
> spellchecker.q makes my multi-word terms checked at the phrase level
> ("mickey mouse") instead of at the word level ("mickey" "mouse") which  is
> the behavior I'm seeking.  the docs make it sound like I could write  my own
> SpellingQueryConverter, but... well, they also use both q and
> spellchecker.q at the same time, so it shouldn't implode like that :)

Hi again, Geoffrey et al,

I've tried this again, nightly build form 2008-06-25... I added the spellcheck component to
my dismax using last-components (very handy!). I find that the following all work as expected

using seperate q and spellcheck.q , documents returned (matching 'soundtrack') and suggestion
(for 'rock')




so far so good :) no null pointers .

{Beto|Norberto|Numard} Meijome

"It is not the strongest of the species that survive, nor the most intelligent, but the one
most responsive to change."
  Charles Darwin.

I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers
makes you go blind. Writing them is worse. You have been Warned.

View raw message