The issue is that you are using an analyzer on the search query and not at
index time. The StandardAnalyzer that you are using at search time is
lowercasing the query before searching against the index. You have a few
options that I can think of:
1 - use a different analyzer at search time (o
order in
user-unexpected ways.
Does the proviso make more sense now?
- J.J. Larrea
On Nov 16, 2009, at 10:36 AM, Jeff Plater wrote:
>
> I am looking at adding some sorting functionality to my application
> and
> read that Sort fields should not be tokenized - can anyone explain
I am looking at adding some sorting functionality to my application and
read that Sort fields should not be tokenized - can anyone explain why?
I have code that is tokenizing the sort fields and it seems to be
working. Is it just because some tokenizing can change the value (like
remove stop word
.
At least carefully check that your casing is identical.
Best
Erick
On Wed, Nov 11, 2009 at 6:41 PM, Jeff Plater <
jpla...@healthmarketscience.com> wrote:
> Thanks - I tried it out and it seems to work for "Philadelphid~0.75
PA" but
> I can't get it working for "P
Thanks - I tried it out and it seems to work for "Philadelphid~0.75 PA" but I
can't get it working for "Phil* PA" yet. Perhaps it is an issue with my
Analyzer (I am using WhitespaceAnalyzer)?. Have you used it with wildcard
before?
-Jeff
-Original Message-
From: AHMET ARSLAN [mailto:
omplish this? Right now I am having to
hit a look up table to translate the city before searching against the
main index - not a fan of this option.
Thanks.
-Jeff Plater
