: I've updated the wording - hopefully it's a little clearer now.
Yeah, but SolrFacetingOverview should probably be updated as well. : counting up terms. This did exist for single valued fields, and now : also exists for multi-valued fields. The implementation is different : of course, but I don't think we need more control over that. If : anything the single-valued implementation could be made a little more : efficient w.r.t memory use. Hmmm... i think i understand: facet.method determines either that enum is used or an univerted field cache of some form (either the lucene FieldCache or the new solr UnInvertedField) is used -- and the specifics are determined by whether the field is multi-tokend? If we do "optimize" the single-value case to use UnInvertedField instead we should definitely add an option for that, since some people may also be sorting on the field (and having an UnInvertedField in addition to a FieldCache could be considered a waste of ram) -Hoss
