I'm having a little trouble following this discussion, first off as to your immediate issue...
: Thanks, but I think I'm going to have to work out a different solution. I : have written my own analyzer that does everything I need: it's not a : different analyzer I need but a way to specify that certain fields should : be tokenized and others not -- while still leaving all other options open. ...maybe there is some terminology confusion here ... if you've already got an "Analyzer" (capital A Lucene classname) then you can specify it for one fieldType, and usethat field type for the fields you want analysis done. if you have other fields were you don't want tokenizing/analysis done, use a differnet fieldType (with a StrField). As for your followup question... : As far as the generic options parsing resulting in unused properties in a : ShcemaField object, not it is not specifically documented anywhere, but : the Solr Wiki lists, for both fields and field types: "Common options that : fields can have are...". I could not find anywhere a definitive list of : what is allowed/used or excluded, so I went to the code and found that the That's because there is no definitive list. Every FieldType can define it's own list of attributes that can be declared and handled by it's own init method. -Hoss
