Thanks, I know I read that sometime back but I guess I thought that was because there were no <analyzer> tags defined on the string field in the schema. I guess cause I'm still kind of a noob - I didn't take that to mean that it couldn't be made to have analyzers. A subtle but important distinction I guess.
So my concern now is that my use case is that I need a field that behaves like string, case-sensitive, and a case-insensitive version of the same. Is it the case the solr.StrField and solr.textField with LowerCaseFilterFactory and KeywordTokenizerFactory only differ by their treatment of character case? -----Original Message----- From: Ahmet Arslan [mailto:iori...@yahoo.com] Sent: Wednesday, January 13, 2010 12:18 PM To: solr-user@lucene.apache.org Subject: RE: case-insensitive string type > That seems to work. > > But why? Does string type not support > LowerCaseFilterFactory? Or KeywordTokenizerFactory? >From from apache-solr-1.4.0\example\solr\conf\schema.xml : "The StrField type is not analyzed, but indexed/stored verbatim." "solr.TextField allows the specification of custom text analyzers specified as a tokenizer and a list of token filters."
