> Alternatively, if one of the "regular" analyzers works for you *except*
> for lower-casing, just use that one for your mixed-case field and
> lower-case your input and send it to your lower-case field.
>
> Be careful to do the same steps when querying .
>
Thanks Erick, I didn't think about this.
See PerFieldAnalyzerWrapper for an easy way to implement two fields
in the same document processed with different analyzers. So basically
you're copying the input to two fields that handle things slightly
differently.
As far as re-implementing stuff, no real re-implementing is necessary,
just crea
> I just want to see if it's safe to use two different analyzers for the
> following situation:
>
> I have an index that I want to preserve case with so I can do
> case-sensitive
> searches with my WhitespaceAnalyzer. However, I also want to do case
> insensitive searches.
you should also make su
you should also make sure the data is indexed twice, once w/ the original
case and once w/o. It's like putting a TokenFilter after WhitespaceTokenizer
which returns two tokens - lowercased and the original, both in the same
position (set posIncr to 0).
On Wed, Aug 12, 2009 at 6:20 AM, Max Lynch w
