One last small note based upon my experience (I warned you I didn't have
much, didn't I?)... use the parser if you can. The last thing I wanted to do
was spend a lot of development time working out all the scenarios... For
instance, if you're building up your clause manually, how sure are you
: This kinda leads me back to my "best practises" question: If Im building
: up the query dynamically based off of several fields (rather than the
: user entering a Lucene Query), Im kind of wondering If I should be using
: query parser at all...?! I keep feeling that maybe I should just be
: buil
om: Marc Dauncey [mailto:[EMAIL PROTECTED]
> Sent: 17 May 2006 15:00
> To: java-user@lucene.apache.org
> Subject: Re: Building queries
>
> I'm working on designing this kind of meta configuration on
> top of some Lucene indexes right now. The company I work for
> has
especially in as regards the toomanylcauses exception.
Hope this gives you some ideas, Dave.
Marc
- Original Message
From: Erik Hatcher <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Wednesday, 17 May, 2006 2:42:04 PM
Subject: Re: Building queries
On May 17, 2006, at
On May 17, 2006, at 8:19 AM, Irving, Dave wrote:
First - thanks for Lucene! I started working with it a few days ago,
bought the Lucene In Action book, and Im very impressed with both.
Thank you for the latter! For the former, thanks go to Doug and many
others.
Im integrating search in t
Hi,
...
>> So, I just need to run the terms entered by the user in each field
>> against the appropriate analyser, and build up the query that way.
>> Does that sound like a sensible approach? Are there any
>> code samples
>> around showing how to run search phrases through analysers
>> and
See below...
1) Are there any "best / common practises" for this that I've missed
during my web searches and reading of Lucene in Action?
OF COURSE there are , but I don't know where they are either..
2) I don't want to release the full query syntax to users: So I'll
probably have multiple
