You can't get 'round this without creating a copyField or similar. It's easy to do in schema.xml Store one field (e.g. 'state') using a fieldType that is configured to use a LowercaseFilterFactory, and the other not (e.g. 'state_verbatim').
When you search, use the lowercase one for case-insensitive searching (e.g. q=state:*) - alaska, AlAsKA, ALASKA, etc. When you facet, use the the non-lowercase one for 'Alaska' (e.g. &facet=true&facet.field=state_verbatim). > All my fields are stored. > > > > And if my field name is "state" means that your suggestion > > is appending > > "fl=state", then no, that's not doing anything for > > me. =( > > > > The above config gets me part of the way to where I need to > > be. Storing, > > for instance, "Alaska" in such a way that querying for > > "alaska", "AlaSkA", > > and "ALASKA" will all return "Alaska". However, if I > > include the field as a > > stats.facet, or I'd doing a faceted search (facet=true), or > > do a terms > > search, what I get out is "alaska". > > > > Any way around that without the dupe field? > >
