Mailing-List: contact lucene-net-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: lucene-net-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=kSEbyPWS75GQe29eBjdUQsceiw+UHZQlqimnTqzoUKEgHbSKcHYoIJQIlA1Y8dMpzqS0ILtSyk94ICAenLHeJO7GeRXWVA1UpKxWahDeCspg+gMf4kDI9M9aB/pXqj+4O3D80icJ7iWhHkm2R6SJiFa2rjIKH2ylspydSMpe0J8=;
Message-ID: <995064.86824.qm@web30505.mail.mud.yahoo.com>
References: <990757.775.qm@web30508.mail.mud.yahoo.com>
 <003e01ca59bb$0cc194d0$2644be70$@com>
Date: Fri, 30 Oct 2009 17:55:05 -0700 (PDT)
From: Ron Grabowski <rongrabowski@yahoo.com>
Subject: Re: Is it generally a good idea to avoid using QueryParser if you
 know how to make the Query yourself?
To: lucene-net-user@incubator.apache.org
In-Reply-To: <003e01ca59bb$0cc194d0$2644be70$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Is there a way to avoid using QueryParser altogether? I don't need all the text parsed, I just want to run the name field through an analyzer and use the output of that along with TermQuerys for the zip and city. I'm wanting to do  ~2,500 specific searches on an index with between 26m documents. I know ahead of time what most of my fields will be. I thought I could save some time by not having to separate  my fields, making a giant string, then having QueryParser split the string back into terms to search.


----- Original Message ----
From: Digy <digydigy@gmail.com>
To: lucene-net-user@incubator.apache.org
Sent: Fri, October 30, 2009 7:45:21 PM
Subject: RE: Is it generally a good idea to avoid using QueryParser if you know how to make the Query yourself?

You can combine queries . (such as your custom "TermQuery" + the result of a
"QueryParser.Parse")

DIGY

-----Original Message-----
From: Ron Grabowski [mailto:rongrabowski@yahoo.com] 
Sent: Saturday, October 31, 2009 1:12 AM
To: lucene-net-user@incubator.apache.org
Subject: Is it generally a good idea to avoid using QueryParser if you know
how to make the Query yourself?

I can convert this text into a Query using  just TermQuery and BooleanQuery:

name:"ACME Produce" AND city:Anytown AND zip:90210

If I create the Query object on my own will I loose all the  benefits from
things like  StandardAnalyzer? Is there a way I can submit an object graph
to QueryParser so I can get the benefits of its analyzer without making it
parse the raw string? My input is coming from well defined areas; its not
free form where the user can enter anything they want.

Can I use a StandardAnalyzer myself then take its output and create the
appropriate Query objects then join all of them into a BooleanQuery?

I'm using /tags/Lucene.Net_2_4_0.