Re: Solr 1.4.1: Weird query results

2011-04-20 Thread Erick Erickson
This is all very strange. I guess I only have a few suggestions: > It might be worth getting a copy of Luke. Under th "tools" menu there's a "checkindex" option that may show you something. You can also use Luke to query your index and examine it. That said, Luke uses Lucene, not Solr so

Re: Solr 1.4.1: Weird query results

2011-04-20 Thread Erik Fäßler
Oooops, I have to take something back: The index *has* been created with Lucene 2.9.3! Sorry for confusing that, I am using two different index versions, the older for productive purposes and the newer for what I am developing currently. I just checked back with Luke, he acknowledges that the

Re: Solr 1.4.1: Weird query results

2011-04-20 Thread Erik Fäßler
Thank you very much for your answers :-) First of all, I just noticed I sent the question unintentionally to the Lucene list while it's more of a Solr issue. I will answer here all the same to not confuse things. My apologies ;) First to Erick's suggestions. The default field has been "text"

Re: Solr 1.4.1: Weird query results

2011-04-19 Thread Lance Norskog
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,

Re: Solr 1.4.1: Weird query results

2011-04-19 Thread Erick Erickson
H, 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

Solr 1.4.1: Weird query results

2011-04-19 Thread Erik Fäßler
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 result