Luke defaults to KeywordAnalyzer when you do a search on it. You have
to specifically choose StandardAnalyzer. You are probably already doing
this, but I figure its worth a check.
Matt
Andrzej Bialecki wrote:
oh...@cox.net wrote:
Hi Phil,
Well, kind of... but...
Then, why, when I do the search in Luke, do I get the results I cited:
xxxx ==> succeeds
xxxx.yyy ==> fails (no results)
I guess that I've been assuming that the search in Luke is "correct"
and I've been using that to "test my understanding", but maybe that's
an invalid assumption?
Luke has some bugs, that's for sure, but not as many as one would
think ;) I recommend the following exercise:
* first, check what the "Rewritten" query looks like, in both cases.
This could be enlightening, because depending on the choice of default
field and query analyzer results could differ dramatically.
* then, if a query succeeds in matching one or more documents, open
this document and view its fields using "Reconstruct & edit",
especially the "Tokenized" version of the field. At this point any
potential mismatch in query terms vs. analyzed tokens in the field
should become apparent.
--
Matthew Hall
Software Engineer
Mouse Genome Informatics
mh...@informatics.jax.org
(207) 288-6012
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org