# Controlling Score on Phrase Suggester

**URL:** <https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167>\
**Category:** Elasticsearch\
**Created:** [January 26, 2018, 8:19am UTC](https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167 "2018-01-26T08:19:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![moy2010](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moy2010/32/22403_2.png) [@moy2010](https://discuss.elastic.co/u/moy2010)\
**Post date:** [January 26, 2018, 8:19am UTC](https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167/1 "2018-01-26T08:19:51Z")

</div>

Hello, ES community and devs. After expending a considerable time with the phrase suggester, I've come to a point where I need to further control it, specially on the phrase scoring part of it.

Besides the smoothing models, are there any plans to allow us to further control the score of the query?

Perhaps, by allowing us to set a string\_distance parameter on a per-term basis, just like in the term suggeter?

Or by having a way to "boost" the terms generated by each of the sections in the direct\_generator (i.e. the terms generated by the first direct generator to have a boost factor of 2, and the ones by the reverse generator a boost factor of 1) ?

I do not know if this goes down to the lucene implementation of the suggester, or if this can be tweaked at the ES implementation level.

Please comment if you have experienced similar issues or wish this kind of cuntionality.

---

<div class="post-metadata">

**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\
**Post date:** [February 2, 2018, 10:04am UTC](https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167/2 "2018-02-02T10:04:43Z")

</div>

there is nothing in the pipeline but you are happy to propose changes and open issues for those. usually it's a good idea to explain what the problem is rather than proposing a specific solution first.

---

<div class="post-metadata">

**Author:** ![moy2010](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moy2010/32/22403_2.png) [@moy2010](https://discuss.elastic.co/u/moy2010)\
**Post date:** [February 2, 2018, 6:26pm UTC](https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167/3 "2018-02-02T18:26:32Z")

</div>

Hi, Simon. The issue I'm facing is that the suggester seems to be scoring based on document matching instead of based on the edit distance, thus forcing me to set the max\_edits generator parameter to 1.

If my assumption about the suggester scoring is correct, then this would be a query that should have a few tweaking params 🙂 .

---

<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 2, 2018, 6:26pm UTC](https://discuss.elastic.co/t/controlling-score-on-phrase-suggester/117167/4 "2018-03-02T18:26:33Z")

</div>

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