Thanks a lot for the solution / explanation. Saved the day Erik.
Summary
Observation: Using a wild carded search term with queryParser and the
WhitespaceAnalyser returned no hits when when hits where expected.
Reason: This was caused by the default behaviour of queryParser to lower
case wildcar
On Nov 17, 2004, at 7:44 AM, [EMAIL PROTECTED] wrote:
I then try a search using the term
ResponseHelper.writeNoCachingHeaders\(*\);
now I'm expecting this to be a wider search term and it should find at
least two, possibly more docs?
the query parser produces the query
+contents:responsehelper.writ
Thanks for the suggestions Erik. Displaying the query string is really
usefull
and this is what i've found.
I issue a search using the search term
ResponseHelper.writeNoCachingHeaders\(response\);
The search is parsed using a query parser and produces the following query
string
+contents:Resp
Try using a TermQuery instead of QueryParser to see if you get the
results you expect. Exact case matters.
Also, when troubleshooting issues with QueryParser, it is helpful to
see what the actual Query returned is - try displaying its toString
output.
Erik
On Nov 16, 2004, at 6:25
Hi,
We have indexed a set of web files (jsp , js , xslt , java properties and
html) using the lucene Whitespace Analyzer.
The purpose is to allow developers to find where code / functions are used
and defined across a large and dissperate
content management repository. Hopefully to aid code re-use
