Disk is cheap, and I can always put the field elsewhere if I need to
sort on it, but user response time ... Priceless. I'll give #1 a shot.
I'm going to try encoding them in the same position, see what happens.
Thanks!
-
To unsu
Would Lucene's FuzzyQuery be useful in this case? I
suppose it would depend on how meaningful the
sequences of numbers are.
http://lucene.apache.org/java/docs/api/org/apache/lucene/search/FuzzyQuery.html
--- Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
> : I could (1) up front, put in both vers
: I could (1) up front, put in both versions of the numbers or (2) during
: query, play with the number and search both ways. What's the best
: practice approach?
In the imortal words of Erik Hatcher...
"It Depends :)"
#1 takes up more space on disk and in memory, and makes it imposibl
For some things, it's obvious that you would have to put them both on
the front end (during indexing) and on the back end. E.g., if you want
to do a soundex search, you'd want to encode the words with their
soundex version during index creation, and when you query incode the
user's search input as
