Doug Cutting wrote:
David Spencer wrote:
2 files attached, SubstringQuery (which you'll use) and
SubstringTermEnum ( used by the former to be
consistent w/ other Query code).
I find this kind of query useful to have and think that the query
parser should allow it in spite of the perception
of
David Spencer wrote:
2 files attached, SubstringQuery (which you'll use) and
SubstringTermEnum ( used by the former to be
consistent w/ other Query code).
I find this kind of query useful to have and think that the query parser
should allow it in spite of the perception
of this being slow,
Subject: Re: SubstringQuery -- Re: Leading Wild Card Search
David Spencer wrote:
2 files attached, SubstringQuery (which you'll use) and
SubstringTermEnum ( used by the former to be
consistent w/ other Query code).
I find this kind of query useful to have and think that the query parser
Hi
I've written a PrefixQuery and it's not hard to do -I can post it too.
Problem is that it is not integrated into the query parser (.jj) so odds
are noone will use it, and the general sentiment on this list (and lucene-dev)
is that prefix queries are evil because it's an expensive operation as
Kristian Hermsdorf wrote:
Hi
I've written a PrefixQuery and it's not hard to do -I can post it too.
Problem is that it is not integrated into the query parser (.jj) so odds
are noone will use it, and the general sentiment on this list (and
lucene-dev)
is that prefix queries are evil because
Flip your text and add it as another field and when the user enters *word
you can search that field for drow*
Wesley
-Original Message-
From: Vipul Sagare [mailto:[EMAIL PROTECTED]
Sent: February 11, 2004 1:54 PM
To: [EMAIL PROTECTED]
Subject: Leading Wild Card Search
Lucene docs,
Vipul Sagare wrote:
Lucene docs, FAQs and other research indicates
Note: Leading wildcards (e.g. *ook) are not supported.
Is there any work around for implementation of such feature (if one has
to implement)?
I've written a PrefixQuery and it's not hard to do -I can post it too.
