Thank you Ian and Jack,
I believe I'll go with simply creating a NumericField for the length, as
that will result in the best performance.
-Camden
On Fri, Jan 21, 2011 at 10:35 AM, Ian Lea wrote:
> Wouldn't that also match names with length > 20?
>
>
> --
> Ian.
>
>
> On Fri, Jan 21, 2011 at 3
Wouldn't that also match names with length > 20?
--
Ian.
On Fri, Jan 21, 2011 at 3:26 PM, Jack Krupansky
wrote:
> A wildcard query with 10 leading question marks, each of which requires a
> single character. This would also depend on leading wildcards being enabled
> in your query parser (if y
: Friday, January 21, 2011 10:26 AM
To: java-user@lucene.apache.org
Subject: Re: Performing a query on token length
A wildcard query with 10 leading question marks, each of which requires a
single character. This would also depend on leading wildcards being enabled
in your query parser (if you are using
A wildcard query with 10 leading question marks, each of which requires a
single character. This would also depend on leading wildcards being enabled
in your query parser (if you are using one.)
first_name:??*
The performance would not necessarily be great, but functionally it would do
Not directly, but you could index a NumericField called "length" and
do a NumericRangeQuery on it.
Or loop through all the terms checking length. But that isn't a query
and will be slow.
--
Ian.
On Fri, Jan 21, 2011 at 3:15 PM, Camden Daily wrote:
> Hello all,
>
> Does anyone know if it is p
