I forgot to mention that my Query.ToString() runs perfect in Luke when using the correct Analyzer.
Chris Martin Software Developer – myKB.com http://mykb.com [EMAIL PROTECTED] +1 602-326-5200 -----Original Message----- From: Joe Shaw [mailto:[EMAIL PROTECTED] Sent: Thursday, March 15, 2007 8:34 PM To: [email protected] Subject: Re: Help With Search Please Hi, Martin, Chris wrote: > I have an application that uses Lucene.net. Up until today, I've had > success using the query 'syntax' until I needed to programmatically > add a TON of clauses to the queries. With ~700 clauses, > QueryParser.Parse is very slow. Definitely. Building queries programmatically using QueryParser is Bad. > So, I turned to the query API, which works absolutely great; except > for one minor thing. I can't seem to get any results (Hits) by > passing the Query object to my Searcher without going through the > QueryParser. > > What in the world am I missing here? I can't find a way to simply > tell any of the players which Analyzer to use. It's hard to saw without seeing the code, but you might want to Console.WriteLine() the query objects to see what the differences are between the one you built by hand and the one handed to you by the QueryParser. Sample code is always helpful too... Joe
