Thanks Erick, indeed your hunch is correct, it's the analyzing filters that facet.prefix seems to bypass, and getting rid of my ASCIIFoldingFilterFactory and MappingCharFilterFactory make it work ok.
The problem is I need those filters... otherwise how should I create facets which match against both Anglicized as well as international prefix spellings? I could of course maintain separate fields and do multiple queries, but seems like that quickly gets out of hand if I also want to support mixed case and other filtering dimensions. Is there a way to route facet.prefix through the field type filters like all the other params? I suppose I could manually instantiate and pre-apply the filters in the client code... any other ideas? -- View this message in context: http://lucene.472066.n3.nabble.com/international-characters-in-facet-prefix-tp4339415p4339534.html Sent from the Solr - User mailing list archive at Nabble.com.
