Use the ngram token filter, and the a query of 512 would match by itself:
http://lucene.apache.org/core/4_9_0/analyzers-common/org/apache/lucene/analysis/ngram/NGramTokenFilter.html
-- Jack Krupansky
-----Original Message-----
From: Erick Erickson
Sent: Thursday, August 28, 2014 11:52 PM
To: java-user
Subject: Re: indexing all suffixes to support leading wildcard?
The "usual" approach is to index to a second field but.... backwards.
See ReverseStringFilter... Then all your leading wildcards
are really trailing wildcards in the reversed field.
Best,
Erick
On Thu, Aug 28, 2014 at 10:38 AM, Rob Nikander <rob.nikan...@gmail.com>
wrote:
Hi,
I've got some short fields (phone num, email) that I'd like to search
using
good old string matching. (The full query is a boolean "or" that also
uses
real text fields.) I see the warnings about wildcard queries that start
with *, and I'm wondering... do you think it would be a good idea to index
all the suffixes? Eg, a phone num 5551234, would become 7 values for the
"phoneNum" field: 4, 34, 234, etc. So "512*" would be a hit.
And maybe do something with the boosts so it doesn't overvalue the match
when it hits multiple values. ?
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
