also, check the LukeRequestHandler
if there is a document you think *should* match, you can see what
tokens it has actually indexed...
On Jun 24, 2008, at 7:12 PM, Norberto Meijome wrote:
hi,
I'm trying to understand why a search on a field tokenized with the
nGram
tokenizer, with minGramSize=n and maxGramSize=m doesn't find any
matches for
queries of length (in characters) of n+1..m (n works fine).
analysis.jsp shows that it SHOULD match, but /select doesn't bring
anything
back. (For details on this queries, please see my previous post over
the last
day or so to this list).
So i figure there is some difference between what analysis.jsp does
and the
actual search executed , or what lucene indexes - i imagine
analysis.jsp only
parses the input in the page with solr's tokenizers/filters but
doesn't
actually do lucene's part of the job.
And I'd like to look into this... What is the suggested approach for
this?
attach a debugger to jetty's web app ? Are there some pointers on
how to debug
at this level? Preferably in Eclipse, but beggars cant be choosers ;)
thanks!!
B
_________________________
{Beto|Norberto|Numard} Meijome
"Always do right. This will gratify some and astonish the rest."
Mark Twain
I speak for myself, not my employer. Contents may be hot. Slippery
when wet.
Reading disclaimers makes you go blind. Writing them is worse. You
have been
Warned.
