TokenFilterFactory clarifications

From my understanding, the system will create a TokenFilterFactory for each
combination between the TokenFilters defined in the configuration file and
each index. If a filter is defined, but not used, an instance will still be
instantiated for each index in the system. Is this scenario correct? What
is the benefit of having a TokenFilterFactory tied to each index if not

Also, is it possible to retrieve all the filters, tokenizers and analyzers?
The variable are private with AnalysisService and can only be retrieve one
at a time if you know the name. IndicesAnalysisService only has the default
filters, tokenizers and analyzers. Currently, I am using an internal
registry for custom filters, but I am hoping to remove any
possible redundancy.



You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
For more options, visit