Hi Erick,
On Tue, Jan 25, 2011 at 1:38 PM, Erick Erickson erickerick...@gmail.comwrote:
Frankly, this puzzles me. It *looks* like it should be OK. One warning, the
analysis page sometimes is a bit misleading, so beware of that.
But the output of your queries make it look like the query is
Frankly, this puzzles me. It *looks* like it should be OK. One warning, the
analysis page sometimes is a bit misleading, so beware of that.
But the output of your queries make it look like the query is parsing as you
expect, which leaves the question of whether your index contains what
you think
Hi Jerome,
does your fieldtype contains a stopword-filter?
Probably this could be the root of all evil :-).
Could you provide us the fieldtype definition and the explain-content of an
example-query?
Did you check the analysis.jsp to have a look at the produced results?
Regards,
Em
Jerome
Try submitting your query from the admin page with debugQuery=on and see
if that helps. The output is pretty dense, so feel free to cut-paste the
results for
help.
Your stemmers have English as the language, which could also be
interesting.
As Em says, the analysis page may help here, but I'd
Hmmm, I don't see any screen shots. Several things:
1 If your stopword file has comments, I'm not sure what the effect would
be.
2 Something's not right here, or I'm being fooled again. Your withresults
xml has this line:
str name=parsedquery+DisjunctionMaxQuery((meta_text:ecol d
ingenieur)~0.01)
Erick,
On Mon, Jan 24, 2011 at 9:57 PM, Erick Erickson erickerick...@gmail.comwrote:
Hmmm, I don't see any screen shots. Several things:
1 If your stopword file has comments, I'm not sure what the effect would
be.
Ha, I thought comments were supported in stopwords.txt
2 Something's not
