# TokenFilterFactory clarifications **URL:** \ **Category:** Elasticsearch\ **Created:** [April 11, 2013, 7:09pm UTC](https://discuss.elastic.co/t/tokenfilterfactory-clarifications/11554 "2013-04-11T19:09:16Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [April 11, 2013, 7:09pm UTC](https://discuss.elastic.co/t/tokenfilterfactory-clarifications/11554/1 "2013-04-11T19:09:16Z")
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 used? 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. Cheers, Ivan -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:41am UTC](https://discuss.elastic.co/t/tokenfilterfactory-clarifications/11554/2 "2017-07-06T02:41:30Z")