Alexandre Rafalovitch wrote > Each field has a type. Each type defines what happens with the text. > You can certainly select to do one thing but not another.
Understood. But it seemed to me that only TextField allows adding filters to it and filters go in conjunction with tokenizers. I could not find a way to add a filter without also adding a tokenizer. And there is nothing like a ready to use null tokenizer. I am using Solr-4.0.0-BETA. Alexandre Rafalovitch wrote > 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). I'm probably missing something. You mean schema.xml from the example? The "string" type is basically an empty reference to StrField. And all of text_* types use one tokenizer or another. I can't find any without a tokenizer. Andrew. -- View this message in context: http://lucene.472066.n3.nabble.com/Untokenized-lowercase-string-tp4010296p4010308.html Sent from the Solr - User mailing list archive at Nabble.com.
