Hi Chris,
On 23.08.2010 21:37, Chris Hostetter wrote:
> : The document is indexed correctly, a search for "at s" found it and all
> : fields looked great ("at&s and not for example, at&s).
> :
> : As my stopword list does not contain "at" or "&" or "&", I don't
> : quite understand, why my result is found, when I disable the
> : stopword-list. My stopwordlist can be found here
> :
> : http://pastebin.com/RfLuBHqd
> :
> : Do you happen to see bad things for a string like "at&s" here?
>
> "s" is in your stopwords file, which may be part of the problem (but i
> didn't look hard at your query string to verify that)
>
> : The analysis page in the admin panel tells me, these steps for the Index
> : Analyzer:
> ...
> : (StopFilter) 1: at&s, at; 2: s, ats => 1: at&s, at; 2: ats
> :
> : So, according to this, it should be found even with my stopwords enabled...
>
> Strange, based on the stopwords file you posted the "s" should definitely
> be getting removed at index time -- it would also get removed at query
> time, but because you have it *before* WDF at query time that wouldn't
> affect this query (even though it did affect the index)
>
> There was a bug with analysis.jsp and stopwords recently, but that
> shouldn't have affected 1.4 (you are definitely using 1.4, correct?)
>
> https://issues.apache.org/jira/browse/SOLR-2051
I am using solr 1.4 (actually LucidWorks Solr) in production and tried
1.4.1 for testing - unfortunately I can't tell for sure, if I tried the
analysis.jsp in both...
I moved the stopword filter before the WordDelimiterFilter - thanks for
your hints, Chris and Yonik!
best regards,
Nikolas Tautenhahn
