lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lance Norskog <>
Subject Re: Solr 1.4.1: Weird query results
Date Tue, 19 Apr 2011 23:07:32 GMT
Look at the "text" definition stack. Does it have the same analyzer
and filter that you used to make the index, and in the same order?

The specific problem is that the "text" field includes a stemmer, and
your code probably did not. And so "marine" is stored as, maybe
'marin'.  To check this out, look at the 'schema browser' page off the
admin page. This will show you all of the indexed terms in each field.
Also look at the Analysis page: this lets you see how text is parsed
and changed in the analysis stack.

On Tue, Apr 19, 2011 at 2:56 PM, Erick Erickson <> wrote:
> Hmmmm, I don't see the problem either. It *sounds* like you don't really
> have the default search field defined the way you think you do. Did you restart
> Solr after making that change?
> I'm assuming that when you say "not created by Solr" you mean that it's created
> by Lucene. What version of Lucene and Solr are you using if that's true?
> You can test this by appending "&debugQuery=on" to your query or checking
> the "debug enable" checkbox in the full query interface from the admin page.
> That should show you exactly what is being searched. You might also want
> to look at the analysis page for your field and see how your query
> is tokenized.
> But, like I said, this looks like it should work. If you can post the results of
> adding &debugQuery=on and your actual <fieldType> definition for "text_ws"
> <field> declaration for "text" and the <defaultSearchField>  from your schema
> that would help. I can't tell you how many times something that's eluded me
> for hours is obvious to someone else :)..
> Best
> Erick
> On Tue, Apr 19, 2011 at 3:59 PM, Erik Fäßler <> wrote:
>>  Hallo there,
>> my issue qualifies as newbie question I guess, but I'm really a bit
>> confused. I have an index which has not been created by Solr. Perhaps that's
>> already the point although I fail to see why this should be an issue with my
>> problem.
>> I use the admin interface to check which results particular queries bring
>> in. My index documents have a field "text" which holds the document text.
>> This text has only been white space tokenized. So in my schema, the type for
>> this field is "text_ws". My schema says
>> "<defaultSearchField>text</defaultSearchField>".
>> When I now search for, say, 'marine' (without quotes), I don't get any
>> search results. But when I search '"marine"' (that is, embraced by double
>> quotes) I get my document hits. Alternatively, I can prepend the field name:
>> 'text:marine' and will also get my results.
>> Similar with this phrase query: "marine mussels", where "In marine mussels
>> of the genus" is a text snippet of a document. The phrase "marine mussels"
>> won't give any hits. Searching for 'text:"marine mussels"' will give me the
>> exact document containing this text snippet.
>> I'm sure this has quite a simple explanation but I'm unable to find it right
>> now ;-) Perhaps you can help with that.
>> Thanks a lot!
>> Best regards,
>>    Erik
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Lance Norskog

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message