Each field has a type. Each type defines what happens with the text. You can certainly select to do one thing but not another.
Just look towards the bottom of the schema.xml and compare field types definition for string and text, it should be fairly obvious. You'll most probably make up a new type and use the definition from the String, but add the lower-case filter. Just make sure that it is added both for indexing and query time if there are two sections in there (don't have my config right here). Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Tue, Sep 25, 2012 at 5:33 PM, am <a...@ejelta.com> wrote: > I am new to Solr. Just wetting my feet, trying to set it up and to migrate > our in-house search to it. > > Is it possible to define a field type that is not tokenized, but has a > lowercase filtering? I'm sure I can do it in java code, but I am looking for > an XML file solution. Basically "Foo Bar" and "foo bar" wants to be the same > thing when stored into that field, but otherwise it wants to behave as > StrField, not TextField. > > > Andrew. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Untokenized-lowercase-string-tp4010296.html > Sent from the Solr - User mailing list archive at Nabble.com.
