Hi,
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.
Im integrating search in to an existing pet-project web application
where new fields for index / search may be added via configuration.
My idea is to have a
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
nylcauses 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
&g
Hi,
Im very new to Lucene - so sorry if my question seems pretty dumb.
In the application Im writing, I've been "struggling with myself" over
whether I should be building up queries programatically, or using the
Query Parser.
My searchable fields are driven by meta-data, and I only want to suppo
s like this may be what you are after.
>
> Otis
>
> - Original Message
> From: "Irving, Dave" <[EMAIL PROTECTED]>
> To: java-user@lucene.apache.org
> Sent: Monday, May 22, 2006 5:15:23 AM
> Subject: Searching API: QueryParser vs Programatic queries
>
queries
>
> If i understand correctly, is it that you dont want to make
> use of query parse?
>
> You need to parse a query string without using query parser
> and construct the query and still want an analyzer applied on
> the outcome search.
>
>
> On 5/22/0 p6
Erick Erickson wrote:
...
> It seems to me that you can always do something like:
> BooleanQuery bq;
> QueryParser qp1 = new QueryParser("field1", "", analyzer);
> Query q1 = qp1.parse("search term or clause); bq.add(q1,,,);
> QueryParser qp2 = new QueryParser("field2", "", analyzer);
> Query q
J.J. Larrea wrote:
> I concur with your thoughts that there is room for such
> utility classes, and that those would increase the use of
> programmatic queries. I say this as a developer who also
> "lazed out" and opted to simply construct a string and let
> the QP do all the work (but who t
Chris Hostetter wrote:
> typically, when build queries up from form data, each piece
> of data falls into one of 2 categories:
>
> 1) data which doesn't need analyzed because the field it's going to
> query on wasn't tokenized (ie: a date field, or a
> numeric field, or a
> boolean
> The QueryParser then adds the -- parsing -- on top of this, but can
delegate for query delegation.
That sould be "query creation", of course.
> -Original Message-
> From: Irving, Dave [mailto:[EMAIL PROTECTED]
> Sent: 23 May 2006 08:30
> To: java-user@lucene
It really helped me out loads and I would recommend it to anyone.
I gave up trying to obtain it from amazon - but got it in 2 days from
Blackwell Online
(http://bookshop.blackwell.co.uk)
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of digby
> Sent: 06 June 2006 11
11 matches
Mail list logo
