# Performance of doc\_values field vs analysed field

**URL:** <https://discuss.elastic.co/t/performance-of-doc-values-field-vs-analysed-field/99445>\
**Category:** Elasticsearch\
**Created:** [September 5, 2017, 2:10pm UTC](https://discuss.elastic.co/t/performance-of-doc-values-field-vs-analysed-field/99445 "2017-09-05T14:10:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ndtreviv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ndtreviv/32/22494_2.png) [@ndtreviv](https://discuss.elastic.co/u/ndtreviv)\
**Post date:** [September 20, 2017, 9:31am UTC](https://discuss.elastic.co/t/performance-of-doc-values-field-vs-analysed-field/99445/4 "2017-09-20T09:31:56Z")

</div>

OK, I've discovered that it should be possible to write a plugin that contains a custom tokenizer.  
It's not a process that's documented anywhere, and I'm hitting problems: [Building a custom tokenizer: "Could not find suitable constructor"](https://discuss.elastic.co/t/building-a-custom-tokenizer-could-not-find-suitable-constructor/101138)

---

_[View the full topic](https://discuss.elastic.co/t/performance-of-doc-values-field-vs-analysed-field/99445)._