To amplify this correct answer, use one field for searching (querying). This would be lower cased. Then use a second field for faceting (case preserved). The only gotcha here is that your original data may have inconsistent casing. My usual answer for that is to either impose a conventional case pattern (which takes you back to one field if you like) or to do a spelling corrector analysis to find the most common case pattern for each unique lower cased string. Then during indexing, I impose that pattern on the facet field.
On Wed, Jan 20, 2010 at 9:46 AM, Erik Hatcher <erik.hatc...@gmail.com>wrote: > Is there a way to maintain case-impartiality whilst allowing facets to be >> returned 'case-preserved'? >> > > Yes, use different fields. Generally facet fields are "string" which will > maintain exact case. You can leverage the copyField capabilities in > schema.xml to clone a field and analyze it differently. -- Ted Dunning, CTO DeepDyve
