# FVH Highlighter Not Being Used By Default

**URL:** <https://discuss.elastic.co/t/fvh-highlighter-not-being-used-by-default/255743>\
**Category:** Elasticsearch\
**Created:** [November 17, 2020, 6:12pm UTC](https://discuss.elastic.co/t/fvh-highlighter-not-being-used-by-default/255743 "2020-11-17T18:12:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jdouty](https://avatars.discourse-cdn.com/v4/letter/j/58956e/32.png) [@jdouty](https://discuss.elastic.co/u/jdouty)\
**Post date:** [November 17, 2020, 6:12pm UTC](https://discuss.elastic.co/t/fvh-highlighter-not-being-used-by-default/255743/1 "2020-11-17T18:12:16Z")

</div>

Hi everyone!

I've been playing around with the FVH and noticed the highlighter isn't behaving as it's described in the [term vector documention](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/term-vector.html).

Down at the bottom of that page it shows that you can use the default highlighter on a field and it will automatically use the FVH highlighter because the term vectors are enabled. But, this isn't what I'm seeing when I try the same thing. The speed of the query and the results match what I'm seeing from the standard default highlighter `unified`.

I wasn't sure if I was just misunderstanding what should be happening or if there was something else on my index that's changing that default highlight behavior?

Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 15, 2020, 6:12pm UTC](https://discuss.elastic.co/t/fvh-highlighter-not-being-used-by-default/255743/2 "2020-12-15T18:12:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.