# Search query returning a different result instead of following the query
**URL:** https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268
**Category:** Elastic Search
**Tags:** elastic-app-search
**Created:** [March 12, 2020, 7:24am UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268 "2020-03-12T07:24:55Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@varunharidas](https://discuss.elastic.co/u/varunharidas)
#### Post date: [March 12, 2020, 7:24am UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268/1 "2020-03-12T07:24:55Z")
I'm trying to search **joseph sunny** but when I type and reach **joseph sun** I'm getting this result which finds a person with just **sun** in the name field. See the screenshots for clarity - running self-hosted.
When i type **joseph sunny** completely
When I reach **joseph sun**
---
### Author:  [@JasonStoltz](https://discuss.elastic.co/u/JasonStoltz)
#### Post date: [March 12, 2020, 11:45am UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268/2 "2020-03-12T11:45:26Z")
Hey @varunharidas ,
I think that's expected. As you can probably imagine, I think our search sees the exact match on "sun" and so scores the document really well.
I'm not sure if there's any way to work around it. If you wanted to, you could probably apply a value boost on the "name" field for "Joseph Sunny", or even create a curation for "joseph sun".
Are you using this for an autocomplete? If so, you could use Query Suggestions which would probably give you the behavior you are looking for.
Otherwise, in my opinion I'd just leave this as is. At the end of the day, do you think this would cause a user to **not** find what they're looking for?
---
### Author:  [@varunharidas](https://discuss.elastic.co/u/varunharidas)
#### Post date: [March 12, 2020, 2:44pm UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268/3 "2020-03-12T14:44:06Z")
Hi @JasonStoltz,
Okay I got it. I think I was using search endpoint for displaying suggestions 🤦🏻♂️
Thanks for pointing it out. Well explained 💥
---
### Author:  [@varunharidas](https://discuss.elastic.co/u/varunharidas)
#### Post date: [March 12, 2020, 2:46pm UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268/4 "2020-03-12T14:46:05Z")
@JasonStoltz Actually this came up after querying from algolia dash, as they are displaying query suggestion when we search in the index from their dashboard. However app-search is using search endpoint dynamically to display results below as they need to show the whole document. Got it now. 👍
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 9, 2020, 2:46pm UTC](https://discuss.elastic.co/t/search-query-returning-a-different-result-instead-of-following-the-query/223268/5 "2020-04-09T14:46:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.