Oh, and yet another way to get around it (with it's own trade offs) is
to use something like fieldtype textTight in the example schema.xml,
which catenates all word parts in both the index analyzer and query
analyzer.
This would index as "upanddownmysitecom" and allow the following
queries to mat
On 12/13/06, Wade Leftwich <[EMAIL PROTECTED]> wrote:
I've run into some unexpected case sensitivity on searches, at least
unexpected by me.
If you index a text field containing this sentence:
A sentence containing CamelCase words by [EMAIL PROTECTED] is found
at StudlyCaps.org
The document wi
> - Original Message
> From: Wade Leftwich <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Wednesday, December 13, 2006 11:32:11 PM
> Subject: Case sensitivity on hostnames and email addresses
>
> I've run into some unexpected case sensitivity on se
- Original Message
From: Wade Leftwich <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Wednesday, December 13, 2006 11:32:11 PM
Subject: Case sensitivity on hostnames and email addresses
I've run into some unexpected case sensitivity on searches, at least
unexpected by me.
If
I've run into some unexpected case sensitivity on searches, at least
unexpected by me.
If you index a text field containing this sentence:
A sentence containing CamelCase words by [EMAIL PROTECTED] is found
at StudlyCaps.org
The document will be found by searching for "camelcase" but not for
"[E
