An Analyzer object is a chain of Tokenizer and TokenFilters. These text type definitions either use an analyzer class or describe the Tokenizer and TokenFilters directly. The Analyzer classes create their own sequence of Tokenizer and maybe TokenFilters, hard-coded in the analyzer class. In schema.xml, you will find text types with Tokenizer/Filter chains, or with just an Analyzer.
Take the Analyzer out of the specification. On Wed, Jul 25, 2012 at 5:19 AM, Ahmet Arslan <iori...@yahoo.com> wrote: > >> When I specify analyzer class in schema, something >> like below and do >> analysis on this field in analysis page : I cant see >> verbose output on >> tokenizer and filters >> >> <fieldType name="text_chinese" >> class="solr.TextField"> >> <analyzer >> class="org.apache.lucene.analysis.cn.smart.SmartChineseAnalyzer"> >> <tokenizer >> class="solr.SmartChineseSentenceTokenizerFactory"/> >> <filter >> class="solr.SmartChineseWordTokenFilterFactory"/> >> </analyzer> >> </fieldType> >> >> >> *But if i don't add analyzer class, I can see the verbose >> output based on >> token and filters applied.* > > Above config is somehow wrong. You cannot use both analyzer combined with > tokenizer and filter altogether. If you want to use lucene analyzer in > schema.xml there should be only analyzer definition. > > It is highly recommended to use solr's charFilter(s), tokenizer, > tokenFilter(s) in schema.xml. > > > -- Lance Norskog goks...@gmail.com
