# Precision tuning does not affect prefixing

**URL:** https://discuss.elastic.co/t/precision-tuning-does-not-affect-prefixing/295291
**Category:** Elastic Search
**Tags:** elastic-app-search
**Created:** [January 25, 2022, 1:49am UTC](https://discuss.elastic.co/t/precision-tuning-does-not-affect-prefixing/295291 "2022-01-25T01:49:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Meaveryway](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/meaveryway/32/100814_2.png) [@Meaveryway](https://discuss.elastic.co/u/Meaveryway)
#### Post date: [January 25, 2022, 1:49am UTC](https://discuss.elastic.co/t/precision-tuning-does-not-affect-prefixing/295291/1 "2022-01-25T01:49:21Z")

</div>

Hello dear community,

While doing search through AppSearch, we notice some aggressive matching patterns that end up highlighting irrelevant words on the search results. The relevant parts of the results are still correctly highlighted and the scoring is alright, but the irrelevant words being highlighted introduces doubt regarding the precision of the search engine from users.

Here's an example in the image (query tester on Kibana, we get the same results through the search API): Basically, the "_de_" is being prefix-matched with a lot of other words. This case is particularly problematic because "_de_" is a stop-word in french and is being matched with a whole lot of words that by times may contradict the query itself and introduce a lot of confusion (for instance, the query includes "_september_" and some results highlight "_december_")

 ![Screenshot 2022-01-25 at 02.07.22](https://us1.discourse-cdn.com/elastic/original/3X/9/b/9bb4557e56f52170eb47e464c41ff94484d1ff40.png)

So it's basically an issue of prefixing. We attempted to address this through the precision tuning feature and it doesn't seem to have an effect on that (the example in the image is actually with a **precision of 11** ). It appears as if the precision parameter isn't having any effect on the results.

Is precision tuning unrelated to highlighting? is it language-dependant? what are other ways to reduce this fuzziness?

As noted in the [documentation](https://www.elastic.co/guide/en/app-search/current/precision-tuning.html#precision-tuning), synonyms aren't being used.

All the stack is on the most recent release (7.16.3)

---

<div class="post-metadata">

### Author: ![Vadim\_Yakhin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vadim_yakhin/32/56723_2.png) [@Vadim\_Yakhin](https://discuss.elastic.co/u/Vadim_Yakhin)
#### Post date: [February 15, 2022, 6:05pm UTC](https://discuss.elastic.co/t/precision-tuning-does-not-affect-prefixing/295291/2 "2022-02-15T18:05:56Z")

</div>

Thanks for the detailed post, Meave!

This indeed looks like a bug.

Although the plans might change, we added it to our near-term roadmap to look into.

---

<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: [March 15, 2022, 6:06pm UTC](https://discuss.elastic.co/t/precision-tuning-does-not-affect-prefixing/295291/3 "2022-03-15T18:06:33Z")

</div>

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